Hey guys!!
We may have a solution to the recovery issue found after updating to the 4.2 build!!
However, someone needs to run some commands in ADB for the TeamWin team.
I am NOT on the 4.2 update or i would do it myself.
But if there is someone on the 4.2 update who isnt very familiar with ADB, i am more than happy to run a TeamViewer remote desktop session to figure this out.
I cannot wait to solve this!
Thanks for reading guys!
elesbb said:
Hey guys!!
We may have a solution to the recovery issue found after updating to the 4.2 build!!
However, someone needs to run some commands in ADB for the TeamWin team.
I am NOT on the 4.2 update or i would do it myself.
But if there is someone on the 4.2 update who isnt very familiar with ADB, i am more than happy to run a TeamViewer remote desktop session to figure this out.
I cannot wait to solve this!
Thanks for reading guys!
Click to expand...
Click to collapse
You don't say what they wanted run.
I will be doing this myself in the next few hours but if someone would like to do it now can they please install terminal emulator from market if you are already on 4.2.1 update and run the following 2 commands and paste the output here.
ls /dev/block
mount
Deleted
flumpster said:
You don't say what they wanted run.
I will be doing this myself in the next few hours but if someone would like to do it now can they please install terminal emulator from market if you are already on 4.2.1 update and run the following 2 commands and paste the output here.
ls /dev/block
mount
Click to expand...
Click to collapse
It's because you need to be on the freenode chat with them while doing it. I don't think it's simply those two commands because they want some commands ran while inside TWRP
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
It's because you need to be on the freenode chat with them while doing it. I don't think it's simply those two commands because they want some commands ran while inside TWRP
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Yea figured that out but can't do it right now. Would help otherwise. The read out from those commands was too long to post. Better to have some who can go freenode to help.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Lol. I give up.
I am one of the devs from the prime forums and was just trying to help you out because I was the person that edited twrp to work on data2sd installs.
I will head back to the prime forums and try to get it to work there instead
flumpster said:
Lol. I give up.
I am one of the devs from the prime forums and was just trying to help you out because I was the person that edited twrp to work on data2sd installs.
I will head back to the prime forums and try to get it to work there instead
Click to expand...
Click to collapse
I'm confused lol. I can't do anything lol. You gotta talk to the guys over at TWRP I was just merely getting volunteers to help out.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Ok I have re-updated to 4.2.1 and seem to have a successful way to now to go back and forth between 4.1.1 & 4.2.1
Here is a screenshot of those two commands "ls /dev/block" & "mount" which shows the partitions still in ext4, which I think blows my theory out the door
I have also been contacted by eyeballer to jump into the twrp on freenode chat but just waiting till were both online
pjc21 said:
Ok I have re-updated to 4.2.1 and seem to have a successful way to now to go back and forth between 4.1.1 & 4.2.1
Here is a screenshot of those two commands "ls /dev/block" & "mount" which shows the partitions still in ext4, which I think blows my theory out the door
I have also been contacted by eyeballer to jump into the twrp on freenode chat but just waiting till were both online
Click to expand...
Click to collapse
Awesome paul!! How do you go back and forth between 4.2 and 4.1? Just flash the different .blob files?
Oh also look for Dees_Troy on freenode. He can help as well. Its who i was talking to.
elesbb said:
Awesome paul!! How do you go back and forth between 4.2 and 4.1? Just flash the different .blob files?
Click to expand...
Click to collapse
First I did a clean wipe from twrp then installed WW_epad-user-10.4.2.20.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed that zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification. I clicked and installed and once the system had rebooted into new android 4.2.1 system I get a triangle notification with a downgrade option to 10.4.2.20
---------- Post added at 12:41 PM ---------- Previous post was at 11:45 AM ----------
Hi,
Have just been talking to Dees_Troy and this is what he had to say
<Dees_Troy> We are going to have to update the kernel
<Dees_Troy> The new bootloader changed something about the partition scheme
<Dees_Troy> I will post a test build tomorrow in the 300 twrp thread
<Dees_Troy> Without the new kernel the entire internal emmc chip doesn't show up at all
<Dees_Troy> Having the new kernel will fix it but I won't be able to patch it to allow backup and restore of boot / kernel until we get source
<Dees_Troy> If you hang around another hour I might have time to make a test build
So where getting somewhere now :good:
Hopefully only a matter of hours or days now till we should have a working recovery with 4.2.1
pjc21 said:
First I did a clean wipe from twrp then installed WW_epad-user-10.4.2.20.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed that zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification. I clicked and installed and once the system had rebooted into new android 4.2.1 system I get a triangle notification with a downgrade option to 10.4.2.20
---------- Post added at 12:41 PM ---------- Previous post was at 11:45 AM ----------
Hi,
Have just been talking to Dees_Troy and this is what he had to say
<Dees_Troy> We are going to have to update the kernel
<Dees_Troy> The new bootloader changed something about the partition scheme
<Dees_Troy> I will post a test build tomorrow in the 300 twrp thread
<Dees_Troy> Without the new kernel the entire internal emmc chip doesn't show up at all
<Dees_Troy> Having the new kernel will fix it but I won't be able to patch it to allow backup and restore of boot / kernel until we get source
<Dees_Troy> If you hang around another hour I might have time to make a test build
So where getting somewhere now :good:
Hopefully only a matter of hours or days now till we should have a working recovery with 4.2.1
Click to expand...
Click to collapse
That is some sexy news! At least we will get root again! omg i think i have a hard on now xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Well I've got a long night ahead of me so I'm thinking about flashing the stock recovery and doing the update
Sent from my SAMSUNG-SGH-I747 using xda premium
---------- Post added at 09:56 PM ---------- Previous post was at 09:44 PM ----------
elesbb said:
That is some sexy news! At least we will get root again! omg i think i have a hard on now xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
+1 x10
Sent from my SAMSUNG-SGH-I747 using xda premium
keep us updated paul!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
keep us updated paul!
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Will do, just waiting to hear back about test build :good:
Here is slightly more detailed method of what I did:
What I did is from running CROMI, I booted into twrp and first I did a clean wipe then installed WW_epad-user-10.4.2.20.zip which can be extracted from the WW_epaduser_10_4_2_20_UpdateLauncher.zip
Downloaded the TF300T_WW_epaduser_10_6_1_8_SDupdate.zip from the Asus website, unzipped and renamed EP201_768_SDUPDATE.zip to WW_epad-user-10.6.1.8.zip, copied to internal sd card and after a few seconds get the triangle update notification in the notification menu of loaded android os.
I clicked and installed and once the system had rebooted into new android 4.2.1 system I get another triangle notification in notification menu with a downgrade option to 10.4.2.20.
If you do not get the notification to downgrade back to 4.1.1 you can try copying the WW_epad-user-10.4.2.20.zip to you internal sd card and you should then get notification after a few seconds.
There is no need to boot into stock recovery, just click on the notification in the notification menu that pop up from loaded android os.
You can boot into fastboot and flash twrp if you want but it will be encrypted/unusable so best to wait for the new build of recovery.
Feel like hugging you man... (no homo) appreciate all your doing... and everyone trying to get this thing working.. was wondering. I have only the new bootloader with the weird fastboot... would this be beneficial to me at all? And im willing to try a fastboot of recovery for testing, lol cause ill be able to tell you fairly quickly whether its working for my type of scenario. .
Lemme know
:thumbup:
Sent from my SPH-D710 using Tapatalk 2
Hmmm... I dont know whats going on man... maybe my bootloader is screwed up. It says it writes it. But again. It seems like the tablet just locks up.. that green box over the rck doesnt flash after writing. No download bar or anything.. there any way to reflash the bootloader as writeable? Or maybe an older version as writeable? Damn this sux..
Sent from my SPH-D710 using Tapatalk 2
Goddly said:
Hmmm... I dont know whats going on man... maybe my bootloader is screwed up. It says it writes it. But again. It seems like the tablet just locks up.. that green box over the rck doesnt flash after writing. No download bar or anything.. there any way to reflash the bootloader as writeable? Or maybe an older version as writeable? Damn this sux..
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
After you are flashing that new twrp.blob are you restarting the tablet before trying to go into recovery ?
The flashing just places it to staging area ready to flash on next restart.
As in .. reboot regular? Power button.. after writing completes I cant reboot from command
Sent from my SPH-D710 using Tapatalk 2
---------- Post added at 01:14 AM ---------- Previous post was at 01:12 AM ----------
It just seems like my bootloader is locking up.... im about to throw this thing against the wall.... I cant do anything with it...
Sent from my SPH-D710 using Tapatalk 2
I'm sorry I'm late, but for the future a little trick. If anyone will run commands in terminal emulator, at the end of command like: ls /dev/block type >/sdcard/lsoutput.txt and then you can post or attach this txt file.
Just to make it a little easier.
If you will do logcat with this txt output don't break it because it runs a little longer until it finishes.
Related
Just bricked a friends TF. Is it possible to unbrick it to stock rom ?
He just updated to latest 3.2WW ROM prior to this.
How exactly did you brick it? What were you doing at the time?
I managed to wipe all partitions .. for various reasons I ran download.sh which apparently formatted the whole TF and reformated it.
At this point I'm downloading the latest tf_rootkit_31 to get the cwm recovery image from it.. but I have my douts that this will work.
I have downloaded the last release from ASUS website and tried to nvflash on the blob files.. but it stays in APX mode..
I have PRIME 1.6r2 but I have no clue how to get this on the device .. without CWM ..
As i thought... didnt work.. but the download.sh wants system.img which I don't have.. :|
think I managed to get it unbricked.
I dumped recovery and system from my working TF101 .. seems to be booting now at least..
This thread can be locked or deleted... as mod see fit
Basically I managed to run the wrong script as I were about to root the TF. Instead of root.sh (self made) that run the needed commands to download, patch and send in the patched boot image back to the TF.
Download.sh is from someone else, don't really who.. but it does wipe the device and flash in boot.img, system.img and recovery.img ..
After fetching the needed files from a working TF101 and flashed it back to the device it is now up and running, but all apps need to be re-installed and setup again.. thankfully he made a mybackup pro backup prior to updating the device.. so I hope he'll managed to restore most of the device back to its original again.
What I love about the TF is that it seems impossible to permabrick. Glad to hear you got it going again.
Glad to hear it. I bricked mine not more than 5 hours ago, and sorted that too.
It's not very nice but you learn as you go I suppose..
(mmh I hate the new mouse-pointer )
Sent from my Transformer TF101 using Tapatalk
Need to pick this up again.. for some reason he doesn't have the 8.4.4.11/8.6.5.7 boot screen.. the one before the boot animation comes into play.. the one he has is the same as 8.4.4.5 .. any1 know the reason and/or a possible fix for this ?
Sent from my Transformer TF101 using Tapatalk
paddy01 said:
Need to pick this up again.. for some reason he doesn't have the 8.4.4.11/8.6.5.7 boot screen.. the one before the boot animation comes into play.. the one he has is the same as 8.4.4.5 .. any1 know the reason and/or a possible fix for this ?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You have to update the bootloader too. It's the EBT partition in the flash.cfg. add something like filename=blob.EBT
You can extract the EBT/bootloader partition from the blob in the 8656 update. Rayman has put out some blob tools for extraction.
sent from my cyanogen(mod) vision
gee one said:
You have to update the bootloader too. It's the EBT partition in the flash.cfg. add something like filename=blob.EBT
You can extract the EBT/bootloader partition from the blob in the 8656 update. Rayman has put out some blob tools for extraction.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Aha perfect, thanks!
Sent from my Transformer TF101 using Tapatalk
paddy01 said:
Aha perfect, thanks!
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
You might want to update the bootloader flag in the command line too "-bl blob.EBT" I'm not positive but I think this prevents bootloops since the images are flashed with the same bootloader that it is writing.
sent from my cyanogen(mod) vision
gee one said:
You might want to update the bootloader flag in the command line too "-bl blob.EBT" I'm not positive but I think this prevents bootloops since the images are flashed with the same bootloader that it is writing.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Thanks a lot for the answers. I haven't got around to do this yet so I have some further questions.. is there a way to do this without wiping the device ?
Also it seems like his Transformer think it's a mobile phone.. eh yea it has like EMEI column and stuff in the information tab.. will the bootloader fix that too ?
the update to 8.6.5.9 didn't appear automatically so we are currently manually updating it to that release.. might fix things.. we'll see..
Edit1: NM! the update to 8.6.5.9 fixed all the issues that were previously
This apparently has been like this for some time but, my daughter has just brought it to my attention.
I have not kept up with this like I should have recently so, Im sure I have forgotten/missed something
Transformer (US) is rooted and on 4.0.3 (9.2.1.11) There is an update available from ASUS but, each time we have tried it, it fails and goes to the exclamation
triangle.
My first thought it is a firmware update from ASUS and the tablet is rooted so it wont take it....am I right or ?
What do I need to do to get her tablet up to date with the latest and greatest? Going to try and read some more on
the forums and see if I can get it figured out.
Thanks ahead of time!
tarheelbuc said:
This apparently has been like this for some time but, my daughter has just brought it to my attention.
I have not kept up with this like I should have recently so, Im sure I have forgotten/missed something
Transformer (US) is rooted and on 4.0.3 (9.2.1.11) There is an update available from ASUS but, each time we have tried it, it fails and goes to the exclamation
triangle.
My first thought it is a firmware update from ASUS and the tablet is rooted so it wont take it....am I right or ?
What do I need to do to get her tablet up to date with the latest and greatest? Going to try and read some more on
the forums and see if I can get it figured out.
Thanks ahead of time!
Click to expand...
Click to collapse
I cant remeber if rooting disables the asus updates. alternativly you can use one of these:
If you have CWM installed you can use this: (http://forum.xda-developers.com/showthread.php?t=1627301)
If you don't have CWM you can use easyflasher: (http://forum.xda-developers.com/showthread.php?t=1688012)
If you want that lastest and greatest u'll need a custom rom :good:
If you have any other recovery or changed any /system/apps you will not be able to do the below. How did you Root your TF?
If you are completely stock with stock recovery, then all you need to do is download OTA Rootkeeper from the market. Open it up, grant SU permission and run it. Once complete, you can hit Temp Unroot and then take the OTA from Settings>About Device. Once your TF is rebooted, then just open OTA Rootkeeper again and hit Restore Root. There you go.
If you do have a custom recovery or changed some /system/apps, then you shoudl follow Jointherealms post. Otherwise there is no need to do all that.
One caveat to OTA Rootkeeper is the latest edition does save a back up of Root however it doesn't save it to /system/xbin anymore for some reason. This can cause some problems with apps looking for Root. So once you get your TF rebooted back up with Root, I suggest going into /system/bin and scroll down and copy SU and paste it in /system/xbin.
Thanks for the replies!
I do have CW recovery installed so, will give that a shot later this evening after work and see what happens.
Appreciate the help...I need to do a better job of keeping up with these things!
Thank you!
Woodrube said:
If you have any other recovery or changed any /system/apps you will not be able to do the below. How did you Root your TF?
If you are completely stock with stock recovery, then all you need to do is download OTA Rootkeeper from the market. Open it up, grant SU permission and run it. Once complete, you can hit Temp Unroot and then take the OTA from Settings>About Device. Once your TF is rebooted, then just open OTA Rootkeeper again and hit Restore Root. There you go.
If you do have a custom recovery or changed some /system/apps, then you shoudl follow Jointherealms post. Otherwise there is no need to do all that.
One caveat to OTA Rootkeeper is the latest edition does save a back up of Root however it doesn't save it to /system/xbin anymore for some reason. This can cause some problems with apps looking for Root. So once you get your TF rebooted back up with Root, I suggest going into /system/bin and scroll down and copy SU and paste it in /system/xbin.
Click to expand...
Click to collapse
JoinTheRealms said:
I cant remeber if rooting disables the asus updates. alternativly you can use one of these:
If you have CWM installed you can use this: (http://forum.xda-developers.com/showthread.php?t=1627301)
If you don't have CWM you can use easyflasher: (http://forum.xda-developers.com/showthread.php?t=1688012)
If you want that lastest and greatest u'll need a custom rom :good:
Click to expand...
Click to collapse
Ok, this failed with the following:
assert failed: apply_patch_check("/system/app/Applocker.odex". "f6e13482721276b130934ecff042404fbf3f5f45". "5197baa5a21df8a69c870f7ea658d6955f18f92e")
E: error in /sdcard/ww-9.2.1.17-to-9.2.1.21-CWM-rooted-v1.0.zip
(status 7 )
Installation aborted.
I read elsewhere in that thread (I think) that this is for .21...did it fail because Im on .11?
Woodrube said:
If you have any other recovery or changed any /system/apps you will not be able to do the below. How did you Root your TF?
If you are completely stock with stock recovery, then all you need to do is download OTA Rootkeeper from the market. Open it up, grant SU permission and run it. Once complete, you can hit Temp Unroot and then take the OTA from Settings>About Device. Once your TF is rebooted, then just open OTA Rootkeeper again and hit Restore Root. There you go.
If you do have a custom recovery or changed some /system/apps, then you shoudl follow Jointherealms post. Otherwise there is no need to do all that.
One caveat to OTA Rootkeeper is the latest edition does save a back up of Root however it doesn't save it to /system/xbin anymore for some reason. This can cause some problems with apps looking for Root. So once you get your TF rebooted back up with Root, I suggest going into /system/bin and scroll down and copy SU and paste it in /system/xbin.
Click to expand...
Click to collapse
Honestly, I dont recall how I rooted it! It has been that long.
I know I have CW 3.2.0.1 on it and as far as I know..it is simply stock rooted. No custom roms and no files changed or deleted (to my knowledge...keep in mind...my 14 yo daughter uses this daily and I havent touched it in several months)
I also dled OTA RK and tried to dl the update and it failed as well. (yellow triangle)
I tried to unroot with RK and check update in system settings but, check firmware tab is not highlighted. I tried to click on the asus system firmware popup and it goes to install...and then comes back to yellow triangle.
Possible she changed deleted something that is causing this to fail?
Try booting into recovery to see if you're still on cwm or not. The yellow triangle sounds like it's stock recovery.
Vol down plus power till you see prompt at left top corner, immediately push Vol up to get into recovery.
baseballfanz said:
Try booting into recovery to see if you're still on cwm or not. The yellow triangle sounds like it's stock recovery.
Vol down plus power till you see prompt at left top corner, immediately push Vol up to get into recovery.
Click to expand...
Click to collapse
Yep, boots into CW recovery just perfectly. Tried to install the files from the sd card in the first post and get the error I posted earlier
tarheelbuc said:
Yep, boots into CW recovery just perfectly. Tried to install the files from the sd card in the first post and get the error I posted earlier
Click to expand...
Click to collapse
Why don't you try installing a custom ROM.... either revolution HD or revolver ICS... both are rooted and tweaked stock ROMS... try them... just be sure to do factory reset/wipe, cache wipe and dalvik wipe before installing any ROM.. good luck
Link for revolution HD ROM
http://forum.xda-developers.com/showthread.php?p=17202357
Link for revolver ICS ROM
http://forum.xda-developers.com/showthread.php?p=23000467
Sent from my Transformer TF101 using xda app-developers app
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
tarheelbuc said:
Yep, boots into CW recovery just perfectly. Tried to install the files from the sd card in the first post and get the error I posted earlier
Click to expand...
Click to collapse
Also one question... where did you download the ROM from ? The one you are trying to flash?
Sent from my Transformer TF101 using xda app-developers app
With CWM you will not be able to apply the OTA update.
You could just flash an update that's in cwm flashable zip
http://forum.xda-developers.com/showthread.php?p=25486812
udupa82 said:
Why don't you try installing a custom ROM.... either revolution HD or revolver ICS... both are rooted and tweaked stock ROMS... try them... just be sure to do factory reset/wipe, cache wipe and dalvik wipe before installing any ROM.. good luck
Link for revolution HD ROM
http://forum.xda-developers.com/showthread.php?p=17202357
Link for revolver ICS ROM
http://forum.xda-developers.com/showthread.php?p=23000467
Sent from my Transformer TF101 using xda app-developers app
---------- Post added at 05:17 AM ---------- Previous post was at 05:15 AM ----------
Also one question... where did you download the ROM from ? The one you are trying to flash?
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I went head and flashed the revolution rom and it went thru perfectly fine..thank you.
I use "my backup" on my Galaxy Nexus to backup before updating and I did the same with the Transformer. Is there anything that is better to use on the TF rather than my backup when updating? Other than that and restoring the apps, everything looks fine at the moment.
In my first post, it wasnt a ROM I was trying to flash, it was an update from ASUS for the firmware. After reading the post for the member below your last post...you cannot do OTA updates after rooting...maybe I had brain freeze or something. She simply brought it to me, I tried to update it, it would not work so, I came here to figure out why!
Maybe it was a "pre-senior" moment I had but, after flashing Revolution...everything is great other than restoring apps!
I do greatly appreciate the help!
baseballfanz said:
With CWM you will not be able to apply the OTA update.
You could just flash an update that's in cwm flashable zip
http://forum.xda-developers.com/showthread.php?p=25486812
Click to expand...
Click to collapse
That right there may have been my issue all along..it is rooted and was running stock but would
not take the OTA...I upgraded to revolution and now everything seems perfectly fine
Thank you for the help!
tarheelbuc said:
I went head and flashed the revolution rom and it went thru perfectly fine..thank you.
I use "my backup" on my Galaxy Nexus to backup before updating and I did the same with the Transformer. Is there anything that is better to use on the TF rather than my backup when updating? Other than that and restoring the apps, everything looks fine at the moment.
In my first post, it wasnt a ROM I was trying to flash, it was an update from ASUS for the firmware. After reading the post for the member below your last post...you cannot do OTA updates after rooting...maybe I had brain freeze or something. She simply brought it to me, I tried to update it, it would not work so, I came here to figure out why!
Maybe it was a "pre-senior" moment I had but, after flashing Revolution...everything is great other than restoring apps!
I do greatly appreciate the help!
Click to expand...
Click to collapse
For restoring apps try titanium backup.. but remember don't backup app data just apps.. coz sometime app data messes ROM up.. if you like to do nand backup then go to recovery and do a backup of the installed ROM.. I always have one coz I have fallback option if I need it.. you can always flash rooted stock ROM but problem with them is, whenever Asus pushed an update you will see them and trying the latest update usually breaks or tablet... so stick with rooted OS.... also try jellybean ROMs when they become stable... much more smoother than ICS....
Sent from my Transformer TF101 using xda app-developers app
Wanted to thank everyone in this thread again. Sorry it has been a couple of days since Iast checked in...life happens! Now, the transformer is screaming along..everything is fine now and my daughter thanks you!
Now let me straggle on over to the Galaxy Nexus forum to see if I want to replace the screen in her Nexus that she just happened to break the day after I got the transformer up and running!
It never ends!
tarheelbuc said:
Wanted to thank everyone in this thread again. Sorry it has been a couple of days since Iast checked in...life happens! Now, the transformer is screaming along..everything is fine now and my daughter thanks you!
Now let me straggle on over to the Galaxy Nexus forum to see if I want to replace the screen in her Nexus that she just happened to break the day after I got the transformer up and running!
It never ends!
Click to expand...
Click to collapse
Hahahaha... sorry but that was just funny so good luck
Sent from my Transformer TF101 using xda app-developers app
I've been trying to get JB on my phone for a while now. I went back to completely stock and got the OTA. Downloaded and I thought it installed. Rebooted, still gingerbread. So I rerooted from scratch. Installed Codename Android on it. Booted up and was running fine for about 5 minutes, at this point I had only signed in to google. Hadn't restored or reloaded any apps. It rebooted on me again. Now. I can't get /sdcard to mount. Fastboot is saying I have no boot.img or recovery, But I can get scroll and click on recovery from that menu. I can't get the ****ing phone to do anything now. I've had this thing rooted since day 1. I'll be honest I really don't know how to use ADB.
Does anyone have any clue how to fix my damn phone?
Format SD through settings, Odin to stock and try again. This time read the instructions carefully... all of them.
Edit: Also make sure drivers are working for adb. Before moving on to another pc, I spent hours one day trying to get adb to work on one of my thinkpads. For whatever reason, I could not get the pad to recognize phone through adb.
Sent from my Nexus S 4G using xda premium
Bruce lee roy said:
Format SD through settings, Odin to stock and try again. This time read the instructions carefully... all of them.
Edit: Also make sure drivers are working for adb. Before moving on to another pc, I spent hours one day trying to get adb to work on one of my thinkpads. For whatever reason, I could not get the pad to recognize phone through adb.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
STOP TALKING ABOUT ODIN!!!!!!!! u dont need that!! just use fastboot commands to go back to stock jellybean! it takes 4 min!!
xda thread: http://forum.xda-developers.com/showthread.php?t=1572307
my vid showing that it works: http://www.youtube.com/watch?v=K4DePKyRgvU
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
[/COLOR]
Cascabreu said:
STOP TALKING ABOUT ODIN!!!!!!!! u dont need that!! just use fastboot commands to go back to stock jellybean! it takes 4 min!!
xda thread: http://forum.xda-developers.com/showthread.php?t=1572307
my vid showing that it works: http://www.youtube.com/watch?v=K4DePKyRgvU&list=UUTsL8yOHOK7IUQl2tsKId5A&index=1&feature=plcp
Click to expand...
Click to collapse
tutorial and download to get drivers working (dont do the root part): http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
What's up with people and fcking odin?
Sent from my Nexus S
kwibis said:
What's up with people and fcking odin?
Sent from my Nexus S
Click to expand...
Click to collapse
i dont now, but what they should know is that when u buy a nexus phone, its made to be easly flash and modified!! = fastboot commands
nexus s isnt a galaxy s2!
Odin, one click toolkits... smh
Odin isnt the best option!!!!!! Fastboot is!
sent from my Nyan NeXus S
"You're either NEXUS or against us!"
I ended up just filing a claim and getting a new-ish one. Mine wouldn't run jellybean to save it's life. Even unrooted and did the OTA update. New one came today and is rocking JB like a champ. I had it rooted about 5 mins after activation.
Thanks to XDA Member noobfordroid we now have the original Boot.img and Recovery.img files that we can use to further our development for this great phone. I plan on taking a better look at them later today, but until then you all are free to check them out! noobfordroid would of posted himself but he doesn't have enough posts to post a link yet.
BOOT IMG
https://www.dropbox.com/s/gq3d442q8hendyp/boot.img
RECOVERY IMG
https://www.dropbox.com/s/k49ll0mjerj84xi/recovery.img
jSterling said:
Thanks to XDA Member noobfordroid we now have the original Boot.img and Recovery.img files that we can use to further our development for this great phone. I plan on taking a better look at them later today, but until then you all are free to check them out! noobfordroid would of posted himself but he doesn't have enough posts to post a link yet.
BOOT IMG
https://www.dropbox.com/s/gq3d442q8hendyp/boot.img
RECOVERY IMG
https://www.dropbox.com/s/k49ll0mjerj84xi/recovery.img
Click to expand...
Click to collapse
awesome i will work on a cwm port ! rite now! i should have it by the end of the week now it would be on the rest of the community on how to flash it as im a noob at recoveries
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
jSterling said:
Thanks to XDA Member noobfordroid we now have the original Boot.img and Recovery.img files that we can use to further our development for this great phone. I plan on taking a better look at them later today, but until then you all are free to check them out! noobfordroid would of posted himself but he doesn't have enough posts to post a link yet.
BOOT IMG
https://www.dropbox.com/s/gq3d442q8hendyp/boot.img
RECOVERY IMG
https://www.dropbox.com/s/k49ll0mjerj84xi/recovery.img
Click to expand...
Click to collapse
if im not mistaken cant we just do this ? http://android-dls.com/wiki/index.php?title=Build_a_custom_recovery_image now that we have the image
cwm recovery
atadres said:
awesome i will work on a cwm port ! rite now! i should have it by the end of the week now it would be on the rest of the community on how to flash it as im a noob at recoveries
---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------
if im not mistaken cant we just do this ? http://android-dls.com/wiki/index.php?title=Build_a_custom_recovery_image now that we have the image
Click to expand...
Click to collapse
I ported the cwm recovery and tried to push it to the phone but it is giving an error.
[email protected]:/home/shyamalapati/android/out/target/product/p8010# fastboot flash recovery recovery.img
sending 'recovery' (6904 KB)...
OKAY [ 1.707s]
writing 'recovery'...
FAILED (remote: Not Support !!)
finished. total time: 1.713s
fails to write smh have u tried to manualy write the recovery image using root explorer on the phone just replace the file in the directory ?
I'm going to have to take a look when I get to my mother in laws. Has anyone tried asking a developer for the Pantech Burst? There may be a simple solution to the issue that we are overlooking.
Sent from my PantechP8010 using Tapatalk 2
EDIT: Also, maybe the recovery partition has a type of lock? Similar to S-ON maybe? I'm going to ask some Pantech Burst developers to see what they have to say.
From doing a few searches with the error it seems to come up often in Pantech phones (other brands as well). It could be the version of CWM or it could just be a locked bootloader issue, or just a bootloader issue. I'm not sure myself but I'm getting my netbook set up with Mint and ditching the VM so I can find out myself.
Sent from my PantechP8010 using Tapatalk 2
EDIT: My VM is up and running now and I'm going to explore. From what I've gathered so far we need to unlock the bootloader to be able to flash anything to the partitions, this can be done with "fastboot oem unlock" I don't know if that command is going to be that easy but I'm going to check it out! If that fails then were going to need to tackle the bootloader first, also for the recovery, Rootzwiki has been a great source, and they have a tutorial for everything we are looking into, there is a command but I can't remember it right now in fastboot that allows us to boot partitions without them effecting the phone. We should try booting the recovery to see if it works, if it works we may need to flash something in the recovery to unlock the bootloader. I might be completely wrong but hopefully the unlock command works.
jSterling said:
From doing a few searches with the error it seems to come up often in Pantech phones (other brands as well). It could be the version of CWM or it could just be a locked bootloader issue, or just a bootloader issue. I'm not sure myself but I'm getting my netbook set up with Mint and ditching the VM so I can find out myself.
Sent from my PantechP8010 using Tapatalk 2
EDIT: My VM is up and running now and I'm going to explore. From what I've gathered so far we need to unlock the bootloader to be able to flash anything to the partitions, this can be done with "fastboot oem unlock" I don't know if that command is going to be that easy but I'm going to check it out! If that fails then were going to need to tackle the bootloader first, also for the recovery, Rootzwiki has been a great source, and they have a tutorial for everything we are looking into, there is a command but I can't remember it right now in fastboot that allows us to boot partitions without them effecting the phone. We should try booting the recovery to see if it works, if it works we may need to flash something in the recovery to unlock the bootloader. I might be completely wrong but hopefully the unlock command works.
Click to expand...
Click to collapse
yeah sounds right youve had an evo before idk when but if ur one of the early users of the froyo root method we had to unlock a bootloader using a certain comand in adb to be able to downgrade to an earlier 2.2 that was rootable before the one clicks came out ill try to find that old evo tutorial and find that command lol there was a video i belive with it and the rootz wiki is what my other link on the other page was supposed to send u to i guess i missed a couple of words in the URL on that other page lol good luck to you keep us updated im glad the flex has gotten a community like ours that can use examples to start from scratch
Command should be "fastboot boot recovery.img". User attn1 from the burst developers said if it boots the recovery we should be able to install it with the recovery. I can also use fastboot on Windows in case anyone is interested. Also can we get the custom CWM posted?
Sent from my PantechP8010 using Tapatalk 2
@noobfordroid could you please PM us a link to your cwm recovery ? wow @jsterrling someone from burst actually replied ive been trying for a while now lol hope we can get this up and going using the fastboot command and that the security measures on this boot loader are not insane like that of HTC
---------- Post added at 11:48 AM ---------- Previous post was at 11:40 AM ----------
Btw any of you heard about the pantech discover coming out soon specs are close to ours but with better hardware like camera and display
Yeah, I actually joined the IRC channel and left a message, he was nice enough to reply back right after I got off of work. I'm probably going to be pretty busy up until Friday with work, I took a lot of time off for other reasons but I'm going to try to work on unlocking the bootloader when I can. Fastboot can be used in Windows just installed the Google USB drivers that come with the SDK and all is well.
We just need a custom CWM which I guess I'm going to start working on unless noobfordroid can post his.
jSterling said:
Yeah, I actually joined the IRC channel and left a message, he was nice enough to reply back right after I got off of work. I'm probably going to be pretty busy up until Friday with work, I took a lot of time off for other reasons but I'm going to try to work on unlocking the bootloader when I can. Fastboot can be used in Windows just installed the Google USB drivers that come with the SDK and all is well.
We just need a custom CWM which I guess I'm going to start working on unless noobfordroid can post his.
Click to expand...
Click to collapse
at the risk of being fired ive been on here at work all day lol i was also at work when me and donovan01 were working on the root for the flex lol im captivated at starting from scratch feels like were all pioneers that our work would prbly help out future pantech users since it seems pantech is trying to become a top tier cell phone company now
atadres said:
at the risk of being fired ive been on here at work all day lol i was also at work when me and donovan01 were working on the root for the flex lol im captivated at starting from scratch feels like were all pioneers that our work would prbly help out future pantech users since it seems pantech is trying to become a top tier cell phone company now
Click to expand...
Click to collapse
Yeah they're showing some nice phones now and this has to be probably the best smartphone I've ever owned, camera aside. They just need to support developers but as soon as they do that ill be a pantech customer for life.
Sent from my PantechP8010 using Tapatalk 2
I will send the link a soon as i get home
Sent from my PantechP8010 using xda app-developers app
fast boot recovery
noobfordroid said:
I will send the link a soon as i get home
Sent from my PantechP8010 using xda app-developers app
Click to expand...
Click to collapse
I tried teh fastboot recovery but it is still booting to the phone. Will try to create the recovery again and try
---------- Post added 9th January 2013 at 12:16 AM ---------- Previous post was 8th January 2013 at 11:40 PM ----------
noobfordroid said:
I tried teh fastboot recovery but it is still booting to the phone. Will try to create the recovery again and try
Click to expand...
Click to collapse
boot.img - http:// db .tt/kKJM0n6z
recovery.img - http:// db .tt/SNmTapqg
cwm recovery - http:// db .tt/k6eVZagS
Awesome, I'll take a look tomorrow. Also boot.img and recovery.img are stock I'm assuming?
EDIT: Post #100!!!
Yes.they are stock
Sent from my PantechP8010 using xda app-developers app
[/COLOR]Ok guys boot into recovery with volume up plus power button! then tap volume up + DOWN at the same time it pulls up a menue with the words reboot system now apply update from external Storage wipe data factory reset apply update from cache and when your rooted a new button comes up that says rooted! lol ? ? and when u press on it it says this device was rooted lol seriously pantech tryinna thruw our warrinties under the bus or what!
cwm recovery
The cwm recovery i posted above is not working. I followed a guide online to port that recovery. Can someone post any tutorial for posting cwm?
Looks like we need to consult the burst.developers. did it just hang at fastboot?
Sent from my PantechP8010 using Tapatalk 2
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html here you go i think youd have to change the repo from gingerbread to ICS u know lol so we dont end up with abad port
hi guys,
I have a SL101.ok here is the problem. I was on CM10 and wanted to switch to other ROMS and kernels. but somehow I got into a boot loop. I flashed JB 4.2 by team EOS, GAPPS for TF101 and elite EOS. yes, I did a full wiped. but no, the tablet refused to boot. I tried the tool made by things-o-doom . Still no luck...i can't access my recovery,cause my volume down button is broken, volume up button is sunk in but still usable... . is my tablet dead?
Sent from my supercharged :tank:
hisname said:
hi guys,
I have a SL101.ok here is the problem. I was on CM10 and wanted to switch to other ROMS and kernels. but somehow I got into a boot loop. I flashed JB 4.2 by team EOS, GAPPS for TF101 and elite EOS. yes, I did a full wiped. but no, the tablet refused to boot. I tried the tool made by things-o-doom . Still no luck...i can't access my recovery,cause my volume down button is broken, volume up button is sunk in but still usable... . is my tablet dead?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
I don't own an SL101. can it be flashed with Nvflash in apx mode? easy flasher?back to stock then root again? look for th stock version here or Maybe @ asus no too sure.
sent from TF101 with Android 4.2.2
---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------
YayYouFixedIt said:
I don't own an SL101. can it be flashed with Nvflash in apx mode? easy flasher?
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
oh that kernel didn't work for me. I think its a 4.1.2 kernel. tty kat kernel if you can get it flashed by usb
sent from TF101 with Android 4.2.2
YayYouFixedIt said:
I don't own an SL101. can it be flashed with Nvflash in apx mode? easy flasher?back to stock then root again? look for th stock version here or Maybe @ asus no too sure.
sent from TF101 with Android 4.2.2
---------- Post added at 07:52 AM ---------- Previous post was at 07:50 AM ----------
oh that kernel didn't work for me. I think its a 4.1.2 kernel. tty kat kernel if you can get it flashed by usb
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
flash by USB? how?
Sent from my supercharged :tank:
hisname said:
flash by USB? how?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
good question. I couldnt see anything about it while googling. but there might still be a way by nvflashing stock no? as long as you can goto apx mode dont give up hope.
sent from TF101 with Android 4.2.2
YayYouFixedIt said:
good question. I couldnt see anything about it while googling. but there might still be a way by nvflashing stock no? as long as you can goto apx mode dont give up hope.
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
yep, I can go into APX mode. but sadly not recovery. damn the volume down button AFAIK most recovery tools here do not support SL101. except the one by things o doom...
Sent from my supercharged :tank:
hisname said:
yep, I can go into APX mode. but sadly not recovery. damn the volume down button AFAIK most recovery tools here do not support SL101. except the one by things o doom...
Sent from my supercharged :tank:
Click to expand...
Click to collapse
did you try these instructions http://mobility.forumsee.com/a/m/s/...asher-install-cwm-root-unbrick-one-click.html
sent from TF101 with Android 4.2.2
---------- Post added at 12:40 PM ---------- Previous post was at 12:25 PM ----------
YayYouFixedIt said:
did you try these instructions http://mobility.forumsee.com/a/m/s/...asher-install-cwm-root-unbrick-one-click.html
sent from TF101 with Android 4.2.2
Click to expand...
Click to collapse
oops thought it said it works but it doesnt
sent from TF101 with Android 4.2.2
You might have to take the tablet apart if you want to manually press the volume down and get into recovery.
Solar.Plexus said:
You might have to take the tablet apart if you want to manually press the volume down and get into recovery.
Click to expand...
Click to collapse
WTF? Take out apart? is there an easier way or something?
Sent from my supercharged :tank:
hisname said:
WTF? Take out apart? is there an easier way or something?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Well, I do not know of any way to get to recovery or APX mode without using the volume buttons. Since you have a SL101, APX mode is pretty useless since the SBK keys are not known to use NVFlash.
If you cannot boot to a ROM, the only way to get to recovery is VOL DOWN and POWER. If your VOL DOWN is not working, you are pretty much not gonna get anywhere if you cannot boot.
Sorry that Asus did not build in an additional back door beyond using the hardware buttons in case you happened to break them.
There's just got be a way to take the tablet apart though.
Solar.Plexus said:
There's just got be a way to take the tablet apart though.
Click to expand...
Click to collapse
Google search for "Asus Slider Teardown":
http://www.techrepublic.com/blog/cr...ardown-solid-tablet-but-not-without-flaws/399
And
http://www.youtube.com/watch?v=JG9gEYRALtU
ok guys, I know this sounds stupid and retarded. I highly doubt that anyone has ever asked such a question in this forum.. The question is:is there any possible way I can brick my SL101??reason I am asking is because I am still covered by my warranty. but ASUS still knows that I rooted my tab because of the team EOS boot animation.
Sent from my supercharged :tank:
I've already sent my rooted tablet to Asus for rebooting problems and they replaced it with no problem. It was still cover by warranty.
Maybe they didn't looked, or just didn't care about it.
No way to be sure it'll be ok for you, but in all case (if you're sure you can't fix the volume-up button by yourself) you're not going anywhere with your tablet.
Good luck.
147keul said:
I've already sent my rooted tablet to Asus for rebooting problems and they replaced it with no problem. It was still cover by warranty.
Maybe they didn't looked, or just didn't care about it.
No way to be sure it'll be ok for you, but in all case (if you're sure you can't fix the volume-up button by yourself) you're not going anywhere with your tablet.
Good luck.
Click to expand...
Click to collapse
+1. I RMA'd my rooted SL101 to TX and had no issues. They asked if they could power it up to verify eveything worked.
D
but it is sitting at team eos boot animation, will Asus not get suspicious or anything?
Sent from my supercharged :tank:
hisname said:
but it is sitting at team eos boot animation, will Asus not get suspicious or anything?
Sent from my supercharged :tank:
Click to expand...
Click to collapse
Depends on if they even check it.
On a side note and not wanting to hijack this thread, my SL101 was bought second hand. Is there a way to see if the tablet is still under warranty?
Solar.Plexus said:
Depends on if they even check it.
On a side note and not wanting to hijack this thread, my SL101 was bought second hand. Is there a way to see if the tablet is still under warranty?
Click to expand...
Click to collapse
Typically it's one year. Hit asus.com and register it. It will tell you.
D
As soon as you see a boot animation adb should be broadcasting, get into an adb shell (if you dont know how, there are many tutorials around) use the command "reboot recovery" and it will reboot straight into recovery.
If you dont see the boot animation or adb is not working, i cant help more sorry, There might be some kind of debugging bridge inside the tablet but that will require some googling and then still its a pretty advanced procedure. Good luck:good:
JoinTheRealms said:
As soon as you see a boot animation adb should be broadcasting, get into an adb shell (if you dont know how, there are many tutorials around) use the command "reboot recovery" and it will reboot straight into recovery.
If you dont see the boot animation or adb is not working, i cant help more sorry, There might be some kind of debugging bridge inside the tablet but that will require some googling and then still its a pretty advanced procedure. Good luck:good:
Click to expand...
Click to collapse
but remember I wiped everything in recovery and flashed a new rom. how could adb be enabled? adb device shows "no device found"
Sent from my supercharged :tank:
hisname said:
but remember I wiped everything in recovery and flashed a new rom. how could adb be enabled? adb device shows "no device found"
Sent from my supercharged :tank:
Click to expand...
Click to collapse
USB Debugging has to be enabled in the ROM, and your cable has to be good. If you have a custom recovery, ADB should also work in there for most things.