Related
breaking..ok, old news: RC30 (jailbreak fix)
http://www.tgdaily.com/content/view/40063/140
Curious about this. Im not in the know enough to do anything with root, but for all of you that have access, if others update, will they be able to use anything that you develop or create with access to root? hopefully....
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
sonikamd said:
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
Click to expand...
Click to collapse
If you look there is another thread where someone else posts what to do... although he hasn't got the files on the forum yet he is having some issues uploading them.
sonikamd said:
I 'm wondering how can I prevent this. I'm in about the same boat as you honda. Root is a stranger to me... But, I'm sure it would suck if I get stuck out side of the loop :/
Click to expand...
Click to collapse
JUST DON'T UPDATE TO RC30. It's that simple.
If you don't understand how to get root, just wait till someone (I would but haven't had time) makes a very detailed yet simple method.
Ah, I'm still running RC19 and have yet to experience Google's update process.
I thought the update was mandatory and done without user input, just a "congratulations, you phone is now a little slower!"
So we can just deny the update with the stock sw?
sonikamd said:
So we can just deny the update with the stock sw?
Click to expand...
Click to collapse
When you get the OTA update, it pops up a message window asking if you want to install. You say either say yes, or "not right now". I think it will keep bugging you to install, and possibly go ahead and automatically install it if you say "not right now" enough times. (I'm not positive about that.. I just remember seeing something like that when I was looking through the source for the updater app).
I think it works like Windows updates, it gives you option to update now or later and if neither is hit in a certain time it will install it automatically. I am going to test this when my update comes. I will hit Update later and see what it does. but i have read others comments saying they never seen the update now or later window and got the new version anyhow.
I'm on the train right now so someone else (or me) can post detailed directions. But if you get root and rename/remove /etc/security/otakeys.zip they (probably) can't update you automatically.
While that file is in place they might be able to upgrade without prompting (anyone want to search the code for info?)
UPDATE: They -can- forcibly update you: http://forum.xda-developers.com/showthread.php?goto=newpost&t=443328
google should wonder ppl do thing themselves...wen they have to come up with 3 update in less than a month....there always worried about security and not functionality..lol...i mean cmon i had to buy a new sdcard jus to get RC 29...cause it sure wasnt commin to me via OTA....i wonder wat i have to do to get RC 30..
SmartBrother90 said:
google should wonder ppl do thing themselves...wen they have to come up with 3 update in less than a month....there always worried about security and not functionality..lol...i mean cmon i had to buy a new sdcard jus to get RC 29...cause it sure wasnt commin to me via OTA....i wonder wat i have to do to get RC 30..
Click to expand...
Click to collapse
Correct spelling and punctuation may be a good place to start
sonikamd said:
Ah, I'm still running RC19 and have yet to experience Google's update process.
I thought the update was mandatory and done without user input, just a "congratulations, you phone is now a little slower!"
So we can just deny the update with the stock sw?
Click to expand...
Click to collapse
Well, I accepted RC29 and I've noticed the phone is faster and has better battery life.
I've also been very conservative with usage because I'm waiting to install and run apps from the SD card.
jailbreaking the t-mobile RC30 update
From what I have read so far it is not possible to re do the images on the G1 because of the RC30 patch from T-Mobile. Mainly because you do not have root, and the second because without root you can't remount the /system partition as RO.
adb allows you to mount the /system partition as RW. Would this not do the trick.
Code:
./adb shell
#mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
This was the out put that I got. Now to run the remount from adb.
Code:
adb remount
-
remount succeeded
now to make sure that this really worked.
Code:
./adb shell
-
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
as you can see the /system directory is not in rw mode and not ro mode.
To test to see if this is the case.
Code:
vi test.push (:wq)
adb push test.push /system
adb shell
# cd /system
# ls
test.push
lib
media
framework
fonts
etc
build.prop
bin
usr
sounds
recovery.img
app
lost+found
As we can see this did seem to work. I do not have a T-Mobile RC30. I have mine jailbroken already. with the steps that JesusFreke laid out.
I was wondering if it would be possible to do the same steps but with using adb to mount the fs in rw, and then using adb push to push the recovery.img to the device into the /system dir.
doing another push of the test.push file seems to take.
Code:
adb push test.push /system
vi test.push (i incerted the leter i)
adb push test.push /system
0 KB/s (2 bytes in 0.048s)
adb shell
# cat /system/test.push
i
#
So this might be the break that people are looking for that have the T-Mobile RC30. JesusFreke I know that you said that you have one with an RC30 from T-Mobile. Would you be willing to try this at the risk of bricking the phone? I know that is a $400 question, or anyone else for that matter.
If you do try it, please let me know the results. I have a friend, whos wife has the RC30 from T-Mobile. He is not willing to risk his wife's wrath.
It works on emulator.exe but will the live RC30 adb server accept remount? I notice that there are no references to remount in the official documentation. Alas I don't have any official RC30 G1 to test with.
Id bewilling to trythis right now. I have a Modded RC30 that I will update to the official RC30 that I am sending back anyways for defects. Anyone wanna tell me how to flash mine back to Official RC30 and Ill get to trying.
mouseclone said:
From what I have read so far it is not possible to re do the images on the G1 because of the RC30 patch from T-Mobile. Mainly because you do not have root, and the second because without root you can't remount the /system partition as RO.
adb allows you to mount the /system partition as RW. Would this not do the trick.
Code:
./adb shell
#mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 ro 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
This was the out put that I got. Now to run the remount from adb.
Code:
adb remount
-
remount succeeded
now to make sure that this really worked.
Code:
./adb shell
-
# mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock3 /system yaffs2 rw 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mmcblk0p1 /sdcard vfat ro,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0
as you can see the /system directory is not in rw mode and not ro mode.
To test to see if this is the case.
Code:
vi test.push (:wq)
adb push test.push /system
adb shell
# cd /system
# ls
test.push
lib
media
framework
fonts
etc
build.prop
bin
usr
sounds
recovery.img
app
lost+found
As we can see this did seem to work. I do not have a T-Mobile RC30. I have mine jailbroken already. with the steps that JesusFreke laid out.
I was wondering if it would be possible to do the same steps but with using adb to mount the fs in rw, and then using adb push to push the recovery.img to the device into the /system dir.
doing another push of the test.push file seems to take.
Code:
adb push test.push /system
vi test.push (i incerted the leter i)
adb push test.push /system
0 KB/s (2 bytes in 0.048s)
adb shell
# cat /system/test.push
i
#
So this might be the break that people are looking for that have the T-Mobile RC30. JesusFreke I know that you said that you have one with an RC30 from T-Mobile. Would you be willing to try this at the risk of bricking the phone? I know that is a $400 question, or anyone else for that matter.
If you do try it, please let me know the results. I have a friend, whos wife has the RC30 from T-Mobile. He is not willing to risk his wife's wrath.
Click to expand...
Click to collapse
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Koush said:
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Click to expand...
Click to collapse
Meaning that as soon as you type in adb shell and hit enter it will not even start the daemon?
Get official RC30 zip (here), use SignApk.jar from AndroidMod.zip (here) on it and place it in root of sdcard as update.zip. Reboot into recovery and Alt+S.
ballaholyk84 said:
Meaning that as soon as you type in adb shell and hit enter it will not even start the daemon?
Click to expand...
Click to collapse
Most likely it just gives the shell at $ instead of #.
Edit: gah, dyslexic.
Koush said:
The RC30 you have from JesusFreke gives the adb daemon root permissions. What you listed will not work on a Google RC30.
Click to expand...
Click to collapse
I was thinking that was just for the adb shell command. The adb remount is something that is in the helpfile from the SDK. Just typing in adb will give you the list of commands to use.
If not going though the shell how ever, did they disable all of adb's root privs? If you have one and try the remount and get a success, the adb still has root privies, just not on with the adb shell command.
Really this is just a thought. I wish that I really had a device to test it on.
kk i am very desperate for help
i have been seeking help regarding rooting my optimus 2x for 2 months
heres the story:
i rooted my phone using superoneclick and everything worked out fine
then i flashed MIUI on my phone and it worked fine except the GPS was very slow
then i had flashed a recovery rom to go back to the stock Froyo
then i flashed Cyanogenmod 7.1 and it worked fine
i saw that MIUI had some new updates and that it was much better than Cyanogenmod in my opinion
So i went to ROM Manager and tried to reboot my phone into recovery but nothing happened at all
I've tried every way to boot into recovery but it goes to the stock recovery
I downloaded a root checker and it tells me my device is not rooted
now when i try to use superoneclick i get stuck
can any1 please help me
i've been posting in the superoneclick forum and no1 has been able to help me for 2 months
lol, use NVflash one click and flash CWM, you dont even need root, flash it then flash another rom.
if that doesnt work: factory reset, unroot, then re-root
Help me too!
I know this is going to sound incredibly dumb (and thats because i barley know anything about all of this stuff)
I've been trying to root my LG G2x for a couple days now, but it just wont work.
Ive followed all the steps to use superoneclick to root my device and the program works as far as i can tell. It finishes step 7 and gives me this message: "Killing ADB and restarting as root... enjoy!"
Unfortunately before i can even use my phone more messages start flowing out. I have absolutely no idea what any of it means, but the program and my phone both crash until i hard boot both so i would really appreciate any help!
This is the message i get: "$
$ export TEMPRANDOM=29169;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount -o rw,remount /system
mount: permission denied (are you root?)
END:29169export PS1=""
export TEMPRANDOM=92557;export PS1=END:$TEMPRANDOM;/data/local/tmp/busybox mount
rootfs on / type rootfs (ro,noatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mmcblk0p1 on /system type ext3 (ro,noatime,data=ordered)
/dev/block/mmcblk0p7 on /data type ext3 (rw,relatime,data=ordered)
/dev/block/mmcblk0p2 on /cache type ext3 (rw,nosuid,nodev,noatime,data=ordered)
tmpfs on /mnt/extasec type tmpfs (rw,noatime,mode=755,gid=1000)
/dev/block/mmcblk0p6 on /nvdb type ext3 (rw,nosuid,nodev,relatime,data=ordered)
/dev/block/vold/179:8 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:8 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/vold/179:17 on /mnt/sdcard/_ExternalSD type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:17 on /mnt/extsecure/extasec type vfat (rw,dirsync,nosuid,nodev,noexec,noatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/_ExternalSD/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
END:92557export PS1=""
"
Yeap.. nvflash works. I tried the oneclick root. And got the same error as below... its a little complicated at first, because you have to do the steps onthe computer with the nvflash . After that i plugin the phone as thesteps and BOOM,no need to root, i am using a custom rom. Its fast my phone with two Dragon inside hell yeaaa....
Sent from my LG-P999 using XDA Premium App
chipis said:
Yeap.. nvflash works. I tried the oneclick root. And got the same error as below... its a little complicated at first, because you have to do the steps onthe computer with the nvflash . After that i plugin the phone as thesteps and BOOM,no need to root, i am using a custom rom. Its fast my phone with two Dragon inside hell yeaaa....
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
can u tell me exactly what u did? like step by step?
nydmt said:
can u tell me exactly what u did? like step by step?
Click to expand...
Click to collapse
Go to the root thread in my signature and then in that thread there is a link to the One Click Recovery Flasher using NVFlash. That thread is detailed, step by step and even has a link to a video. Not to be a smartass, but if you cannot follow that thread to install recovery on the phone then you should not be flashing roms on your phone. This is basic stuff you need to know and understand first or you are going to royally screw up your phone.
Can Someone do this!!
Connect ur Tab & Start adb & Run following commands
adb shell
cat proc/partitions
cat proc/emmc
and Pm me the Output!
Sent
Sent from my GT-P5113 using Tapatalk 2
zapote21 said:
Sent
Click to expand...
Click to collapse
You beat me to it... My wife just got one of these - she's not interesting in rooting, etc., but I am (and may buy one) if the new model allows. Let me know if I can be of help.
Anyone know yet if the bootloader is unlocked/unlockable on this model?
LavaJoe said:
You beat me to it... My wife just got one of these - she's not interesting in rooting, etc., but I am (and may buy one) if the new model allows. Let me know if I can be of help.
Anyone know yet if the bootloader is unlocked/unlockable on this model?
Click to expand...
Click to collapse
Its Samsung. Odin is your friend...lol
One more
adb shell
adb mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p7 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
So is this good? Root or toot ?
Pp.
Delivered to you via microwave technology .
I have posted this thread to hopefully sort some of the confusion around the new 4.2.1 update & the seemingly encrypted custom recoveries (twrp & cwm) in an attempt to stop some people before they brick.
In doing testing of the new 4.2.1 ota update (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader. It will not work with any custom recovery. Twrp will give password prompt and be unable to mount anything but possibly system. Same goes for cwm, minus the password prompt.
After doing a full wipe from twrp 2.4.3.0 and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted - can't mount anything.
I believe the reason why the new 4.2.1 bootloader encrypts custom recoveries or rather seems to encrypt so nothing can be mounted, is as follows:
After reading through some of the posts in the twrp thread with similar issues, it seems that twrp looks for these partitions (data, system, cache, etc) to be in a certain format, ie ext4. However if the format twrp is looking for does not exist (say the ext4 is now ext3) twrp will assume that it is encrypted and will bring up a password prompt and be unable to mount.
To confirm – the testing I have done - flashing just the new 4.2.1 bootloader and nothing else - encrypts the custom recoveries. I believe the new 4.2.1 bootloader is reformatting these partitions to some other format, making twrp & cwm assume that these partitions are now encrypted.
I have posted a method here that has worked for me twice now after a full wipe in twrp (cache, dalvik-cache, factory-reset, system, internal storage & data) and then flashing just the 4.2.1 bootloader & rebooting to find an encrypted recovery. Not sure if this will work for everyone but as I said it has worked for me twice now after unsuccessful 4.2.1 bootloader tests.
I have successfully updated to 4.2.1 and downgraded back to 4.1.1. The way that I reverted back from fully working 4.2.1 to 4.1.1 was I received an ota update notification after the 4.2.1 update to revert back to 4.1.1 (10.4.2.20). I have an unlocked device and that is why I am reluctant to reflash the 4.2.1 update again, in case I am unable to downgrade back to 4.1.1 this time.
If anyone is currently running 4.2.1, could you please let me know what format/ext your partitions are in so I can confirm this theory.
I hope this information is helpful and shows why the custom recoveries seem encrypted.
Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
I also am on 4.2.1 with unlocked bootloader. Of course haven't received and option to revert back by ota but i do have the 4.1.1 firmware downloaded just haven't attempted to apply it as for the so many issues with everyone else jist being safe for the moment. I haven't rooted the device yet but am willing to take a shot at going back to 4.1.1 since i have the unlocked bootloader if you think it may work or is it different since you've only flashed the 4.2.1 bootloader. Like said stock firmware 4.2.1 with unlocked bootloader.
Edit: In should add i have no access to fastboot because no pc at the moment. Thats why been hesitant because if brick then I'm screwed all together. I may just wait till more research done on this or definite fix or root is found.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Before doing bootloader tests I did flash the full 4.2.1 ota update, so I was running android 4.2.1 and then rebooted into fastboot and flashed twrp to find that I could not mount, rebooted and let android system load, had a play around with the new ui and new launcher and then received a notification for a system update, already running the latest update thought what's this, clicked on it and message popped up saying update to downgrade back to 10.4.2.20 (4.1.1) so that's how I got back to 4.1.1
Not sure why I got this ota downgrade being unlocked but I did not receive 4.2.1 update on device, I downloaded the us ota in the threads used that to manually update in order to do a system dump.
If your running 4.2.1 at the moment could you have a look at what format your partitions are in and post results so I can pass this on to custom recovery devs in order to get working custom recovery with 4.2.1
Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
pjc21 said:
If your running 4.2.1 at the moment could you have a look at what format your partitions are in and post results so I can pass this on to custom recovery devs in order to get working custom recovery with 4.2.1
Click to expand...
Click to collapse
Yes i could where would i look though i don't have a custom recovery its's stock let me know. Any thing to help.
Im not a total noob had many androids in the passednjust new to this one actually been out of game for about a year so jb is new to me and learning again with this.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
I typed a command to get file system info looks like it comes up ext4 but here take a look.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
FWIW in this kind of situation, the decrypt prompt from TWRP doesn't mean that the device is actually encrypted. If TWRP can't mount /data then we assume that it is encrypted. This might seem like a bad way to do it, but that's how Android does it (believe me, I've seen the code in AOSP). Anyway, no one in Team Win has a TF300, so if you want a solution you'll have to come by #twrp on freenode and be able to use things like adb in both Android and in TWRP.
I probably won't check this thread again, so posting here isn't a good way to get hold of me.
Mods, can we make this sticky? Lots of folks are trying to flash custom recoveries then root after the 4.2.1 update and it's obviously not possible yet. Could point folks here from all those other threads before we see more bricks?
aerdely said:
I typed a command to get file system info looks like it comes up ext4 but here take a look.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
If you type "mount" into the terminal it should display the system, data & cache.
On 4.1.1 system is ext4, and looks the same on 4.2.1 and this was the only partition I could mount in twrp after update.
Re: 4.2.1 update & custom recovery issue, encrypted & can not mount (twrp/cwm)
Screw this! I'm unlocked on 4.1.1 and will stay that way for now lol. Not taking this crap update.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Is this were I should watch for updates on CWM fix for 4.2.1 on the TF300T?
Well this sucks. I tried TWRP 2.2.05 and 2.5 as well as like 5 flavors of CWM and nothing... does anyone know if there is anything similar for the Tf101 and Tf700? Sometimes they have the same issues. This really sucks as I cannot root... any ideas???
Most likely not. Try using TWRP 4.2.1, look for it for the TF300t. Not sure if CWM is even going to be released anytime soon considering its mainly developed for the TF101.. Cheers. Going to try TWRP myself and see if it works.
PS: If you do try to flash TWRP, make sure you flash the right version as others can potentially brick your device due to the new bootloader (My guess is the same applies to CWM)
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
pjc21 said:
If your running 4.2.1 at the moment could you have a look at what format your partitions are in and post results so I can pass this on to custom recovery devs in order to get working custom recovery with 4.2.1
Click to expand...
Click to collapse
Hello,
I think I am having the same kind of problem.
Nice thing, I can still boot the stock 4.2.1 presumably flashed from stock WW_epad-10_6_1_27_1-UpdateLauncher.zip.
So, with this sequence:
tab start directly to recovery
adb -d reboot-bootloader
select android guy, and start
adb -d shell once I the second ASUS logo
I can now do a:
$ mount
With the following result:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Problem for me is that the tab boots, then reboots after 30 / 40 seconds of inactivity. :-/
le.jhe said:
Hello,
I think I am having the same kind of problem.
Nice thing, I can still boot the stock 4.2.1 presumably flashed from stock WW_epad-10_6_1_27_1-UpdateLauncher.zip.
So, with this sequence:
tab start directly to recovery
adb -d reboot-bootloader
select android guy, and start
adb -d shell once I the second ASUS logo
I can now do a:
$ mount
With the following result:
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 rw,nosuid,nodev,noatime,errors=panic,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
tmpfs /Removable tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Problem for me is that the tab boots, then reboots after 30 / 40 seconds of inactivity. :-/
Click to expand...
Click to collapse
Reflash stock ROM!
das chaos said:
Reflash stock ROM!
Click to expand...
Click to collapse
I'm just cautious about my next move. In between, I have reflashed the stock 4.2.1 bootloader and I'm out of the boot loop.
I think that the definitive move to get out of the boot loop was :
fastboot wipe misc
Just after that, the tab was booting back to the OS. The problem is that OS still reboots.
I might try to reflash the stock 4.2.1 , but I'm a bit afraid of not beeing able to install any custom recovery or other rom after that.
Can someone confirm / infirm that when back to stock 4.2.1 (), it is still possible to use a custom recovery (CWM, TWRP,...) ?
le.jhe said:
I'm just cautious about my next move. In between, I have reflashed the stock 4.2.1 bootloader and I'm out of the boot loop.
I think that the definitive move to get out of the boot loop was :
fastboot wipe misc
Just after that, the tab was booting back to the OS. The problem is that OS still reboots.
I might try to reflash the stock 4.2.1 , but I'm a bit afraid of not beeing able to install any custom recovery or other rom after that.
Can someone confirm / infirm that when back to stock 4.2.1 (), it is still possible to use a custom recovery (CWM, TWRP,...) ?
Click to expand...
Click to collapse
When you flash stock ROM you can of course flash custom recovery. Newest TWRP is 2.8.5.0.
First I would try to wipe cache and dalvik and flash a new kernel. If that fails, you can go back to stock.
das chaos said:
When you flash stock ROM you can of course flash custom recovery. Newest TWRP is 2.8.5.0.
First I would try to wipe cache and dalvik and flash a new kernel. If that fails, you can go back to stock.
Click to expand...
Click to collapse
In the meantime, with the bootlop-to-system tab healed itself . It now boots to stock 4.2.1 in a stable way (with /data wiped, but I asked that at some point..). I will try to go with twrp. The stock 4.2.1 recovery is still broken but Start+Vol-down still works. Thank's for the info.
le.jhe said:
In the meantime, with the bootlop-to-system tab healed itself . It now boots to stock 4.2.1 in a stable way (with /data wiped, but I asked that at some point..). I will try to go with twrp. The stock 4.2.1 recovery is still broken but Start+Vol-down still works. Thank's for the info.
Click to expand...
Click to collapse
Stock ROMs don't have a recovery - at least not one we would call so. On power + vol down + vol up there will be shown dead android with rudimentary functions. That's why it is better to flash custom ROM.
Hi everyone,
I have a bricked Asus A80, which is repairable if someone has the skills. But I don't. So I need someone's help.
I have tried a lot of procedures but none of them have worked. I will display the details below.
For the one who will give me the correct procedure to unbrick my phone, I will pay him 30$ with Paypal. A small buck, but I have nothing more right now. And all effort deserves reward.
Thanks for your assistance.
Problem :
- Phone stuck on boot screen with the message "Invalid Kernel !" written on the top of the screen.
Pros
- I can access fastboot
- I can boot custom recovery from fastboot
- I can access ADB from booted custom recovery
- I have another working Asus A80 to dump stuff if needed
Cons
- I can't boot to stock recovery
- Flashing complete roms from booted custom recovery works but does not change anything
- I can't flash boot.img nor recovery.img, or at least I did not succeed
Here is all the historic of what I've tried, what worked and what did not, with all the error messages :
http://padfoneclub.com/pl/forum/forum_viewtopic.php?12268.15
This where I am right now. So anyone willing to help?
Thanks guys.
Hello... I read your link. Maybe you are trying to write in a Read only partition(FAILED remote: Security is Enable, close 'flash' function !!)... Try to remount it like Read/Write...! But first you need to know the mount points.. To do that type:
Code:
adb shell su
adb mount
You will get some mounts points. So find the partition you want to mount and type:
Code:
adb mount -o rw,remount <mount point> <pertition name>
For example on SGS3 device the mount point of system is /dev/block/mtdblock3. So the command is:
Code:
adb mount -o rw,remount /dev/block/mtdblock3 /system
Are you that you have an insecure kernel and that your bootloader is unlocked...?
First of all, thanks for answering, I'm grateful. :good:
So the anwser is that no, bootloader is not unlocked, since I actually bricked my phone using Asus' unlocking tool apk. It did not unlock the bootloader, and it corrupted my recovery. And that's why I have this invalid kernel message (I guess).
And since I've tried flashing half a dozen roms after that, I don't have root access anymore. So I can't get su commands to work.
I tried your procedure, and here is what I've got :
Code:
C:\Android>adb shell su
/sbin/sh: su: not found
C:\Android>adb shell
~ # su
su
/sbin/sh: su: not found
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,nodev,noati
me,nodiratime,data=ordered)
~ #
So it seems every partition is read/write...
Okay then try thiw command and post the results..!
Code:
adb shell
adb cat /proc/mount
But if don't have root privileges then I think it's difficult to unbrick it...
If you can root it again by custom recovery...?
Yeah I know, that's why I've been struggling. Asus A80 has almost not dev community, so I have close to 0 solution. Bootloader unlocking is acheived with an app, for root I used framaroot...No root package to flash...But since I have another working Asus A80, maybe I can work something out?
So here are the results :
Code:
C:\Android>adb shell
~ # ←[6ncat /proc/mount
cat /proc/mount
cat: can't open '/proc/mount': No such file or directory
~ # ←[6n
Oh you write wrong the command it's:
Code:
adb shell
adb cat /proc/mounts
It's mounts not mount...!
Lol ok now it's working :
Code:
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p30 /data ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p30 /sdcard ext4 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p25 /cache ext4 rw,relatime,data=ordered 0 0
~ # ←[6n
Okay I get condused...! I can't see the /system partition...! I don't know what is going on. I will try to root it again. Can you still boot onto recovery mode and install zips...?
Well that would explain certain things...But I dont' know why it doesn't not show up since I flashed several official roms and it did work the whole process to the end...
I can boot to CWM or TWRP, but not sure if I can flash unsigned code...
I can sign zips for CWM recovery...! But I don't know what files I have to install. I will inform you when I find out. I'm working on it..! :good:
When you boot on CWM can you mount the /system partition form there.I think there is an option tha you can mount /system
Yes it works, I can mount/unmount /system, or at least I have no error message when I do so...
Let me know if you need any other information or to try something else. :good:
Ok first I want you to try again the command:
Code:
adb shell
adb cat /proc/mounts
And then turn off you device and run the command
Code:
adb logcat > C:/Users/xxxx/Desktop/logcat.txt
When you execute this command turn on your device until you the error then open the file an tell me what it says.
To tell you the truth if we can't see the system partition it's difficult to unbrick it becuase we can't root it..!
When I do this, adb is stuck hanging on 'waiting for device'. When I turn it on, it shows splash screen with the 'Invalid Kernel' error message, but not adb access, only fastboot. To get adb access, I boot to cwm with "Fastboot boot recovery.img"...
What is your rom version...?
Just giving a suggestion, you said you tried flashing a new kernel and boot.img but nothing happened. How exactly did you flash these images?
I could not remember so I just flashed this one :
http://dlcdnet.asus.com/pub/ASUS/Mo...ity/WW_PFI_user_11_8_10_24_UpdateLauncher.zip
And CWM log for the flash was :
Code:
Restarting adb...
Finding update package...
Opening update package...
Installing update...
Writing sbl3 image...
Writing rpm image...
Writing sbl2 image...
Writing sbl1 image...
Writing tz image...
Writing aboot image
Writing modem image...
And then it just stopped, no reboot, it is written "script succeeded, result was [t]" under the droid...But I don't know if everything was properly formated and written...
After that, I tried mounts again, here is the result :
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /storage type tmpfs (rw,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,nodev,noati
me,nodiratime,data=ordered)
~ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /storage tmpfs rw,relatime,mode=050,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/fuse tmpfs rw,relatime,mode=775,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nodev,noatime,nodira
time,data=ordered 0 0
~ #
Do you have everything you need? I can do other stuff if you want. Remember that I have another Padfone Infinity, with root access, if you want to compare partitions...
TheArc said:
Just giving a suggestion, you said you tried flashing a new kernel and boot.img but nothing happened. How exactly did you flash these images?
Click to expand...
Click to collapse
Hello, thanks for your message.
I have access to fastboot, so I just boot the custom recoveries with "fastboot boot recovery.img".
I have cwm, twrmp, 4.1 stock recovery, and 4.4 stock recovery available. I can boot them, but not flash them.
On your other phone can you run the mount commands and post me the result..?
Thank you..!
Ok I just need to charge it a little bit. I will let you know in less than an hour.
Beretta93 said:
Hello, thanks for your message.
I have access to fastboot, so I just boot the custom recoveries with "fastboot boot recovery.img".
I have cwm, twrmp, 4.1 stock recovery, and 4.4 stock recovery available. I can boot them, but not flash them.
Click to expand...
Click to collapse
I believe you're supposed to place the boot.img in the adb folder and do this "fastboot flash boot boot.img" that will flash a new image.