This is a touch recovery, recovery source is from carliv. This is his recovery I compiled it for intel x86, more specifically for Dell Venue 8 (3830), This is a cwm 6.0.5.1 recovery.
Below link is to carliv's thread, this link explains about the recovery, so rather than just copy and paste I linked to his thread. [emoji14][emoji14]
http://forum.xda-developers.com/android/development/port-carliv-touch-recovery-v3-0-porting-t2970150
You need to already be rooted and have flashed unlocked_firmware provided by SDC
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot reboot
Recovery is flashable via fastboot,
Download recovery
http://www.mediafire.com/download/o928o4l92f45wh2/carliv_touch_recovery.img
to install
boot into fastboot
fastboot flash recovery carliv_touch_recovery.img
Credits
carliv
Social-Design-Concepts
Pavel Moravec
Koush
Angel666
Shakalaca
QuBeX
moonbutt74
does adb work?
i get DellVenue8. . . unauthorized
joanthanmajh said:
does adb work?
i get DellVenue8. . . unauthorized
Click to expand...
Click to collapse
Yes, adb works, adb works in all my recoveries.
Code:
[email protected]:~/Desktop$ adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~/Desktop$ adb shell
# exit
[email protected]:~/Desktop$ adb devices
List of devices attached
DellVenue8000242287 recovery
[email protected]:~/Desktop$
Sent from my Venue 8 3830 using Tapatalk
vampirefo said:
Yes, adb works, adb works in all my recoveries.
Code:
[email protected]:~/Desktop$ adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~/Desktop$ adb shell
# exit
[email protected]:~/Desktop$ adb devices
List of devices attached
DellVenue8000242287 recovery
[email protected]:~/Desktop$
Sent from my Venue 8 3830 using Tapatalk
Click to expand...
Click to collapse
adb works just fine for me also, adb has worked on all your recoveries including the tethered version.
I think @joanthanmajh uses windows and doesn't have his drivers installed for recovery. When I used windows I had to install drivers while in recovery mode to get adb to work in recovery.
vampirefo said:
This is a touch recovery, recovery source is from carliv. This is his recovery I compiled it for intel x86, more specifically for Dell Venue 8 (3830), This is a cwm 6.0.5.1 recovery.
Below link is to carliv's thread, this link explains about the recovery, so rather than just copy and paste I linked to his thread. [emoji14][emoji14]
http://forum.xda-developers.com/android/development/port-carliv-touch-recovery-v3-0-porting-t2970150
You need to already be rooted and have flashed unlocked_firmware provided by SDC
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot reboot
Recovery is flashable via fastboot,
Download recovery
http://www.mediafire.com/download/o928o4l92f45wh2/carliv_touch_recovery.img
to install
boot into fastboot
fastboot flash recovery carliv_touch_recovery.img
Credits
carliv
Social-Design-Concepts
Pavel Moravec
Koush
Angel666
Shakalaca
QuBeX
moonbutt74
Click to expand...
Click to collapse
Hey Vamp, thanks for this recovery, I just pulled this from your github to compare with mine, compiles and works correctly.
What font do you use? Mine seems too big. Also do you know of any other unlocked Intel tablets?
Dell V8 3830
tomtom1265 said:
Hey Vamp, thanks for this recovery, I just pulled this from your github to compare with mine, compiles and works correctly.
What font do you use? Mine seems too big. Also do you know of any other unlocked Intel tablets?
Dell V8 3830
Click to expand...
Click to collapse
I will have to look when I get home, next one above default, I can't remember what default is, I want to say I used 10 x 30, see if default is 10 x 24, if it is then I used 10 x 30.
I only have two Intel tablets, dell version same as your, unlocked, other is iview and it is locked, I don't know of any other device first hand that is unlocked.
sent from my kingSing T1 via taptalk
@vampirefo
Have you considered compiling a ROM?
tomtom1265 said:
@vampirefo
Have you considered compiling a ROM?
Click to expand...
Click to collapse
I think @social-design-concepts posted he was working on one, as for me a week ago, I would have said no, complete waste of my time. But if Alexander Weggerle (Intel) keeps his word, then yes I will do what I can to build, compile, port a rom.
vampirefo said:
I think @social-design-concepts posted he was working on one, as for me a week ago, I would have said no, complete waste of my time. But if Alexander Weggerle (Intel) keeps his word, then yes I will do what I can to build, compile, port a rom.
Click to expand...
Click to collapse
found it : well we find out over the weekend just finished putting my build box back together .
tomtom1265 said:
@vampirefo
Have you considered compiling a ROM?
Click to expand...
Click to collapse
Well still no word from Alex, I did go ahead and download aosp. It's way behind cm, wouldn't compile on my crunch machine, so I booted into old mint, it's a year since I used it, downgraded java on it now all ok as far as compiling, I am compiling now, on this old os will take a while.
I still wait for Alex to post his info, I can then add his changes to my build.
Sent from my Venue 8 3830 using Tapatalk
Well it appears to have completed. I got things to do now, but will test later, I guess many things wont work, might not even boot, lol.
It's a start and with Alex's info if he does follow through, the rom should work correctly.
I have
boot.img
recovery.img
system.img
aosp_yellowtail-ota-eng.vampirefo.zip
Code:
building image from target_files RECOVERY...
running: mkbootfs -f /tmp/targetfiles-5v9f0y/META/recovery_filesystem_config.txt /tmp/targetfiles-5v9f0y/RECOVERY/RAMDISK
running: minigzip
running: mkbootimg --kernel /tmp/targetfiles-5v9f0y/RECOVERY/kernel --ramdisk /tmp/tmpmeS15E --output /tmp/tmpNDbXm_
building image from target_files BOOT...
running: mkbootfs -f /tmp/targetfiles-5v9f0y/META/boot_filesystem_config.txt /tmp/targetfiles-5v9f0y/BOOT/RAMDISK
running: minigzip
running: mkbootimg --kernel /tmp/targetfiles-5v9f0y/BOOT/kernel --ramdisk /tmp/tmp6mknmP --output /tmp/tmppIGHf7
running: imgdiff -b /tmp/targetfiles-5v9f0y/SYSTEM/etc/recovery-resource.dat /tmp/tmp0Peb9v /tmp/tmp7V6HcO /tmp/tmpHmBpBw
running: openssl pkcs8 -in build/target/product/security/testkey.pk8 -inform DER -nocrypt
running: java -Xmx2048m -jar out/host/linux-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /tmp/tmpGjf1v8 out/target/product/yellowtail/aosp_yellowtail-ota-eng.vampirefo.zip
done.
Just doing some quick research, if the Dell venue 8 3830 is intel atom z2580 and the 3730 is z2560, it looks as though that is the only difference (exempt obvious screen size difference).
That being said, shouldn't the same method be used to unlock Dell venue 7 as well ?
yohan4ws said:
Just doing some quick research, if the Dell venue 8 3830 is intel atom z2580 and the 3730 is z2560, it looks as though that is the only difference (exempt obvious screen size difference).
That being said, shouldn't the same method be used to unlock Dell venue 7 as well ?
Click to expand...
Click to collapse
I don't have a Dell venue 7, if I did I would have already tried it, you may try if you like, of course if it fails you are on your own.
I'm very tempted, what should I investigate prior to doing this ? ... I don't expect a step by step tutorial but if you can give me the jist I'll do some research.
If I can always get back into the bootlauncher I can recover stock roms again using the toolkit, if there's a chance it'll brick I want to do some serious digging and cross referencing. Am I on the right track in thinking I need to extract some things and compare how the partitions are mapped between the 2 devices?
Appreciate your guidance!
yohan4ws said:
I'm very tempted, what should I investigate prior to doing this ? ... I don't expect a step by step tutorial but if you can give me the jist I'll do some research.
If I can always get back into the bootlauncher I can recover stock roms again using the toolkit, if there's a chance it'll brick I want to do some serious digging and cross referencing. Am I on the right track in thinking I need to extract some things and compare how the partitions are mapped between the 2 devices?
Appreciate your guidance!
Click to expand...
Click to collapse
It works but you'll have no display until the device goes to sleep and you wake it up they're are a number of other stability issues as well. Over mounting mmc emmc sleep of death.
The chips being different is a big deal in and of its self now through in gpio and touch controllers screen controllers.
Then through in the fact that there are different versions of the 2560 and 2580 chips depending on features of the soc and pin out.
Way more diff under the hood than just the screen and chip.
But yes the basic process for unlocking is the same if we only had the needed ifwi file.
If you didn't know I have the 3730 so I've already explored this over and over again.
If you use this option be sure your familiar with the xfstk downloader and the unbricking process I have the files in the myKIT_BATCH thread
@vampirefo sorry my post was non related to the touch recovery care if I test it in the tethered environment
vampirefo said:
You need to already be rooted and have flashed unlocked_firmware provided by SDC
Click to expand...
Click to collapse
I cannot find the unlocked_firmware anywhere? Could you please explain what this means? Also, I couldn't get to it with the link that was provided. XDA 404'd me
ElmoRapz said:
I cannot find the unlocked_firmware anywhere? Could you please explain what this means? Also, I couldn't get to it with the link that was provided. XDA 404'd me
Click to expand...
Click to collapse
It's in the very first post.
Sent from my Venue 8 3830 using Tapatalk
I looked at it and I think the link was down. And I'm not finding it anywhere else
Sent from my A0001 using XDA Free mobile app
ElmoRapz said:
I looked at it and I think the link was down. And I'm not finding it anywhere else
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
vampirefo said:
This is a touch recovery, recovery source is from carliv. This is his recovery I compiled it for intel x86, more specifically for Dell Venue 8 (3830), This is a cwm 6.0.5.1 recovery.
Below link is to carliv's thread, this link explains about the recovery, so rather than just copy and paste I linked to his thread. [emoji14][emoji14]
http://forum.xda-developers.com/android/development/port-carliv-touch-recovery-v3-0-porting-t2970150
You need to already be rooted and have flashed unlocked_firmware provided by SDC
http://www.mediafire.com/download/d6bzc09ghz4ooc3/Venue_8_DevEdition-KK-ASSETS.zip
fastboot flash dnx CLVP_CYAB_P801_FwDnX_vF9.6C_ww42_005.bin
fastboot flash ifwi CLVP_CYAB_IFWI_vF9.6C_ww42_005_P801_wifi_uos.bin
fastboot reboot
Recovery is flashable via fastboot,
Download recovery
http://www.mediafire.com/download/o928o4l92f45wh2/carliv_touch_recovery.img
to install
boot into fastboot
fastboot flash recovery carliv_touch_recovery.img
Credits
carliv
Social-Design-Concepts
Pavel Moravec
Koush
Angel666
Shakalaca
QuBeX
moonbutt74
Click to expand...
Click to collapse
recovery is off
Related
I am unsuccessfully trying to flash any Ubuntu touch daily onto my N7 tilapia. I followed the instructions from Ubuntu wiki for tilapia step by step. The fastboot method ended up with terminal saying "waiting for device" while the N7 booted into fastboot mode by itself. I waited for several hours, nothing happened. Manual install method in recovery aborted because the zip is for grouper and won't install on tilapia.
Can someone please help me? As a long-term Ubuntu user on PC and laptop I am eagerly waiting for Ubuntu touch on a tablet. Thanks in advance!
Sent from my Nexus 7 using xda premium
fleckhansi said:
I am unsuccessfully trying to flash any Ubuntu touch daily onto my N7 tilapia. I followed the instructions from Ubuntu wiki for tilapia step by step. The fastboot method ended up with terminal saying "waiting for device" while the N7 booted into fastboot mode by itself. I waited for several hours, nothing happened. Manual install method in recovery aborted because the zip is for grouper and won't install on tilapia.
Can someone please help me? As a long-term Ubuntu user on PC and laptop I am eagerly waiting for Ubuntu touch on a tablet. Thanks in advance!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
How are you flashing ubuntu? Is phablet-flash not working?
Thanks for your answer. I got it working now. Phablet-flash did not work, so I installed via multiboot.
Sent from my Nexus 7 3G using xda premium
Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
rafatz said:
Hi devs,
I've started to port CM11 4.4 to my beloved Original Padfone (A66).
The first step was to compile the kernel sources that ASUS made available (Kernel 3.4), which as far as I understand will work with KitKat.
Am I correct to assume this?
Also, if the kernel compiled correctly what will be the next steps to test it (flash) in my device? The bootloader is unlocked, but I'm still with the original recovery. I think I will have to flash CWM or simmilar, right?
Thanks!
Click to expand...
Click to collapse
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
The 3.4 kernel should work with KitKat. In order to properly test any CM11 builds you'll have to compile Clockworkmod Recovery for your device first by pulling your stock recovery.img and then compiling Clockworkmod Recovery using that. Additionally to test your kernel the best way is to take the zimage that's produced from compiling the kernel and make a boot.img out of it and boot it using fastboot. Let me know if you still have questions I'll be happy to answer them.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
rafatz said:
I've follow the XDA University guide for building CWM, at http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
But the second step is failing:
Step 2 : Now that the otatools are ready, we need to get a dump of our current boot.img. To do this, use ‘adb shell’ and launch this command
“ dump_image boot /sdcard/boot.img “
This command do not exist in my phone.
Do you have any tip on this?
Thanks in advance!
Click to expand...
Click to collapse
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
shimp208 said:
You have a couple of options of obtaining your stock recovery image (It's better to use your stock recovery.img rather then boot.img when compiling recovery as the recovery.img has more information in it that will make process of building an actual working recovery image easier) the easiest way is to boot into stock recovery, wipe cache in recovery, then reboot the phone. Then from adb run the following command:
Code:
cat /cache/recovery/last_log
This should give you an output, if you read the logfile you will see that one of the partition blocks is called /recovery. Record the name of the recovery partition block and then run the following command:
Code:
su
cat /dev/block/{name=of-recovery-partition-block} > /mnt/sdcard/recovery.img
This will dump a copy of your stock recovery.img to your internal storage. That you can then use to continue in the CWMR compiling process. By all means if you still have questions let me know I'm here to help.
Click to expand...
Click to collapse
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
rafatz said:
OK, I was able to successfully compile CWMR, but when booting to recovery I only get a blank screen and the devices reboots to Android. Is there a way to find any information on the error?
I know that TWRP works in padfone, but I'm not sure if they are compatible.
Click to expand...
Click to collapse
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
shimp208 said:
It's possible that something is wrong with your recovery's graphics. Try taking the zimage of the kernel sources you compiled and swapping that zimage with the one in your CWMR recovery.img (Replace the zimage in your CWMR .img with the one you obtained when compiling the kernel source from ASUS). You could also try compiling TWRP and seeing that results in the same problem there are times on devices TWRP has been working before CWMR was working properly.
Click to expand...
Click to collapse
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
rafatz said:
No way Simply not working
But TWRP is 100%
I've tested the original recovery back and it is perfect as well.
Only CWMR is not working
I've even used the builder tool without success.
I've followed this guide:
http://www.imajeenyus.com/computer/20130301_android_tablet/android/unpack_repack_recovery_image.html
and this
http://forum.xda-developers.com/showthread.php?t=1877807
Anyway, do you think that TWRP will work to flash my CM11 (if I ever build one)?
I think that the next problem is related on how to get the proprietary binaries from the phone to place in the vendor/asus/padfone folder.
Click to expand...
Click to collapse
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
shimp208 said:
The CWMR builder tool has been not working for a while now. If you were able to compile the latest version of TWRP and you said it was working 100% then that will be fine to test your CM11 test builds. For getting the vendor files I would take a look at this guide on the Cyanogenmod wiki regarding porting and pull vendor files. A extract-files.sh script for a pre-existing device such as the Sprint Galaxy Nexus is a decent place to start for getting an idea how to setup extract-files.sh.
Click to expand...
Click to collapse
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
rafatz said:
Yes, TWRP is 100% working
I've checked the extract scripts but my main problem is to identify in the filesystem which files I should pull.
Anyway, I tried to use the "chipset" method and "guess" based on the system information which files/drivers I would need, but that was not very helpfull (http://specdevice.com/showspec.php?id=0429-3576-ffff-ffffa98be330).
Well, I'll continue my studies on this
Click to expand...
Click to collapse
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
shimp208 said:
Another suggestion would be to take a look in the /vendor folder on your device to extract the proprietary files and use that as a starting point to build off. Then you could try and compile a test build using that. Studying other devices device tree's is like you said another way to gain hints about what to do for your own device.
Click to expand...
Click to collapse
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
rafatz said:
HURRAY!
This saved the day
https://www.codeaurora.org/cgit/qui...tree/proprietary-blobs.txt?h=aosp-new/idea133
It is not for Padfone, but it is close enough.
Click to expand...
Click to collapse
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
shimp208 said:
Awesome! Glad you could find a very similar device, best of luck on your CM11 builds :good:.
Click to expand...
Click to collapse
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
rafatz said:
After a few attempts I was able to finish a build for CM 10.2, but it will not boot
I found that maybe I did something wrong with the fstab.padfone, using the new standards with 5 settings instead of only 3.
Well, in order to eliminate these kind of problems, I will make a CM10.1 building, which still uses the old standards.
Click to expand...
Click to collapse
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
shimp208 said:
Does it not boot at all or does it get to the boot-animation at least? Did you try pulling a log to see if you could get any information on the problem? But best of luck on your building :good:.
Click to expand...
Click to collapse
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
rafatz said:
SO far I couldn't even flash the ROM
TWRP is build with name A66, and the ROM is based on padfone.
I tried to change it, but the build fails
I think that I need to continue my efforts to make a working CWMR. So far the issue is the same, I can build and flash the recovery, but it simply do not enter the recovery. I get a flash on the screen and the phone automatically reboots to enter android.
I wonder if there's any way to get logs or more information from this error, so I can at least start to understand why CWMR is not booting.
fastboot boot recovery.img fails as well.
Bad day
Click to expand...
Click to collapse
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
shimp208 said:
To clarify the ROM fails to flash in recovery what is the error it gives you when it fails to flash? To get ADB working on your CWMR build so you can pull log information add these lines in the correct place to your init.rc file in your recovery ramdisk:
Code:
service adbd /sbin/adbd recovery
disabled
socket adbd stream 660 system system
# Always start adbd on userdebug and eng builds
on property:ro.debuggable=1
#write /sys/class/android_usb/android0/enable 1
#start adbd
setprop service.adb.root 1
# Restart adbd so it can run as root
on property:service.adb.root=1
write /sys/class/android_usb/android0/enable 0
restart adbd
write /sys/class/android_usb/android0/enable 1
Click to expand...
Click to collapse
Thanks man! I was able to get a working CWMR.
The GITHUB I created for the device is at:
https://github.com/rafatzbr/android_device_asus_A66
I was able to build CM10.1 to Padfone, but it simply wont boot
stucked in the initial screen (not the bootanimation).
Any help is much appreciated.
Thanks!
** UPDATE **
Still stucked in boot screen
Any ideas?
rafatz said:
** UPDATE **
Still stucked in boot screen
Any ideas?
Click to expand...
Click to collapse
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
shimp208 said:
The ROM build? If it's still stuck pull a log file and post the upload of the log here.
Click to expand...
Click to collapse
Thanks!
The problems is that the device is not in a bootloop. It is stucked in the first screen (on nexus devices it's the first google screen).
How I can get any logs from there, and which logs I would need?
Hello,
My name is ali, I am here trying to make a cwm recovery for your beloved device, and since I did not have this device, so you can help me to try and give the results.
because lg does not recognize FAT partitions, You can try to create an ext2 partition on your sdcard ext then use this method to install recovery : forum.xda-developers.com/showthread.php?p=52214999
Here is the link of recovery (update.zip) : update.zip
Please provide the results asap, and do with your own risk.
This won't work as there is no way to unlock bootloader or bypass locked bootloader yet.
Will have to try and backup my phone first before doing this, this is my primary device
Edit: why is there 2 scripts in the folder?
One says phil the other one is yours.
Update:
Updater-script is phils
Updater-script~ is your's
Please fix this before testing, you have different mounting points in each also.
Sent from my LG-D620 using XDA Free mobile app
Garcia98 said:
This won't work as there is no way to unlock bootloader or bypass locked bootloader yet.
Click to expand...
Click to collapse
You've tried it ? until you say does not work?
plageran said:
Will have to try and backup my phone first before doing this, this is my primary device
Edit: why is there 2 scripts in the folder?
One says phil the other one is yours.
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
i'm use @Olegator methode for that..maybe no need to push that script..but trust me, it will not make a problem.
Sent from my GT-I8262 using XDA Free mobile app
This device's bootloader is locked and noone knows how to unlock it. If someone installs a custom image (kernel, recovery, etc) then the bootloader will detect it and cancel the bootup.
plageran said:
Will have to try and backup my phone first before doing this, this is my primary device
Edit: why is there 2 scripts in the folder?
One says phil the other one is yours.
Update:
Updater-script is phils
Updater-script~ is your's
Please fix this before testing, you have different mounting points in each also.
Sent from my LG-D620 using XDA Free mobile app
Click to expand...
Click to collapse
.~ is backup file when we editing some file on linux..and not a problem.
Sent from my GT-I8262 using XDA Free mobile app
It doesn't work, i tested it, it gives me the bootloader error since it's still locked but it was worth a try.
Update
Hi Guys
Here's Ali's recovery file with a possible fix, I hope it won't brick my device over the weekend.
Alifilth, I still think the update script file you got in your original is a possible cause.
Edit:
Alifilth, your zip file is buggy as hell, normally I can trace files but you got:
"# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/etc/install-recovery-2.sh"
and a recovery.img file that's suppose to do what?
This file is not recommended to anyone and I'm removing the file that I uploaded.
Not working here:
Code:
Finding update package...
Opening update package...
Verifying update pckage..
E:footer is wrong
E:signature verification failed
Installation aborted.
Zaaap
---------- Post added at 07:06 PM ---------- Previous post was at 06:37 PM ----------
Try the recovery.img itself:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Result:
Device can not boot to recovery, it displays:
[520] fastboot_init()
[620] USB init opt @ 0xffe0000
[640] udc_start()
LG logo shown ... I waitet 5 minues at that stage .. nothing.
Normal reboot worked.
dd back my original recovery
So I think my bootloader is unlocked but I don't know since I have nothing to test.
Zaaap
Zaaap72 said:
Not working here:
Code:
Finding update package...
Opening update package...
Verifying update pckage..
E:footer is wrong
E:signature verification failed
Installation aborted.
Zaaap
---------- Post added at 07:06 PM ---------- Previous post was at 06:37 PM ----------
Try the recovery.img itself:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Result:
Device can not boot to recovery, it displays:
[520] fastboot_init()
[620] USB init opt @ 0xffe0000
[640] udc_start()
LG logo shown ... I waitet 5 minues at that stage .. nothing.
Normal reboot worked.
dd back my original recovery
So I think my bootloader is unlocked but I don't know since I have nothing to test.
Zaaap
Click to expand...
Click to collapse
It probably is since it didn't display a "Security Error".
You should try adb reboot bootloader. And fastboot devices while it displays that and when the logo appears.
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
You should try adb reboot bootloader. And fastboot devices while it displays that and when the logo appears.
Click to expand...
Click to collapse
Only leads to a normal reboot.
Zaaap
ali.filth said:
Hello,
My name is ali, I am here trying to make a cwm recovery for your beloved device, and since I did not have this device, so you can help me to try and give the results.
Click to expand...
Click to collapse
Hi @ali.filth,
I flashed your recovery.img but it didn't work.
What do you need to fix it?
Regards,
Zaaap
Hi @ali.filth,
Here you can find the files for LG G2 mini D620.
We now have definitely an unlocked bootloader!
Original D620 files on Mediafire:
build.prop http://www.mediafire.com/view/s262zkw2649f9a9/build.prop
boot.img http://www.mediafire.com/download/2kku32gim2rje87/boot.img.zip
recovery.img http://www.mediafire.com/download/deab8s8e6qajtni/recovery.img.zip
So please help us with a custom recovery.
Thank you.
Zaaap
Zaaap72 said:
Hi @ali.filth,
Here you can find the files for LG G2 mini D620.
We now have definitely an unlocked bootloader!
Original D620 files on Mediafire:
build.prop http://www.mediafire.com/view/s262zkw2649f9a9/build.prop
boot.img http://www.mediafire.com/download/2kku32gim2rje87/boot.img.zip
recovery.img http://www.mediafire.com/download/deab8s8e6qajtni/recovery.img.zip
So please help us with a custom recovery.
Thank you.
Zaaap
Click to expand...
Click to collapse
still havnt got my device back from service so cant try this out.
but have a look here zaaap:
trwp: http://forum.xda-developers.com/showthread.php?t=1943625
CWR: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
invaderjohn said:
still havnt got my device back from service so cant try this out.
but have a look here zaaap:
trwp: http://forum.xda-developers.com/showthread.php?t=1943625
CWR: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Click to expand...
Click to collapse
I tried the cwm one.
Set up a build machine with ubuntu.
Installed toolchain as recommended on source.android.com.
Downloaded cm11 sources and followed the instructions.
The recovery.img was build successful but doesn't boot.
Had not time to look for a reason.
I'll try again on the weekend.
Zaaap
Zaaap72 said:
I tried the cwm one.
Set up a build machine with ubuntu.
Installed toolchain as recommended on source.android.com.
Downloaded cm11 sources and followed the instructions.
The recovery.img was build successful but doesn't boot.
Had not time to look for a reason.
I'll try again on the weekend.
Zaaap
Click to expand...
Click to collapse
Please look up Loki_patch? this is suppose to help inject the recovery on to our devices.
http://forum.xda-developers.com/showthread.php?t=2300021:good:
plageran said:
Please look up Loki_patch? this is suppose to help inject the recovery on to our devices.
http://forum.xda-developers.com/showthread.php?t=2300021:good:
Click to expand...
Click to collapse
@Zaaap72 has hacked the bootloader (aboot) for the G2 Mini.
No need for Loki any more
I must've missed something somewhere, my bad.
Update:
ok i'm screwed, many tuts require a synced CM repo, which I can't afford. 20 GB's of data is alot of cash, which i don't have.
Vagelis1608 said:
@Zaaap72 has hacked the bootloader (aboot) for the G2 Mini.
No need for Loki any more
Click to expand...
Click to collapse
plageran said:
I must've missed something somewhere, my bad.
Update:
ok i'm screwed, many tuts require a synced CM repo, which I can't afford. 20 GB's of data is alot of cash, which i don't have.
Click to expand...
Click to collapse
We also have working custom recovery: HERE
You can chose between CWM, TWRP or PhilZ touch.
Zaaap
Zaaap72 said:
We also have working custom recovery: HERE
You can chose between CWM, TWRP or PhilZ touch.
Zaaap
Click to expand...
Click to collapse
how did you unlock your bootloader? sorry for the questions, just not alot of info online currently
found it thanks
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Hello
Here is attached link to TWRP 2.8.7.0 for Qualcomm's version of 64bit htc_a51ul and htc_a51tuhl. Not sure if it will work with htc_a51dtul (dual sim version for India/Asia) but if someone want to test, please do.
To flash phone, use below fastboot as HTC was change version for 64bit bootloader, so if You use Linux on Your PC, get My version, put together with recovery.img in same folder, restart phone into bootloader and execute:
Code:
chmod 755 fastboot
Code:
./fastboot flash recovery recovery.img
NOTE that dot and slash are IMPORTANT. If You skip it, will not use My fastboot but other which probably not work and You will get error flashing.
If You are on windows, please use latest version of fastboot for windows.
As usual, TRWP sources are on Omnirom github, device sources are on My github.
NOTE THAT YOU NEED TO HAVE 64bit BOOTLOADER (Lollipop installed on device)
Happy rooting
CAUTION: I am not responsible if You delete and/or brick Your device!!!
DOWNLOAD
EDIT1: attach removed due to bug inside. Will attach new one asap fix bug and recompile.
EDIT2: attach attached back
RESERVED
Screenshoots
Thank you fergy!
I will test a51_dtul!
Working
HTC Desire 820 cihazımdan Tapatalk kullanılarak gönderildi
Works great. Thank You!
Now i can backup to ext. sdcard and restore from ext. sdcard. Big evolution.
@fergy:
Great work.
No adb. Is it disabled in the build?
tomal said:
@fergy:
Great work.
No adb. Is it disabled in the build?
Click to expand...
Click to collapse
No adb? Hmm... Wasnt disable it...try to unpack and check please as i am not home atm.
Htc_a51dtul test is normal, but still the same problem, choose to "reboot to recovery" will be Repeated restart to recovery!
kinghunki said:
Htc_a51dtul test is normal, but still the same problem, choose to "reboot to recovery" will be Repeated restart to recovery!
Click to expand...
Click to collapse
I prefer to disable "reboot to recovery" (until there is a fix). It will save many user.
tomal said:
I prefer to disable "reboot to recovery" (until there is a fix). It will save many user.
Click to expand...
Click to collapse
Yes That's what I think!
I think the cause of the problem may be HBOOT!
@fergy,I added the Chinese language
Hi, where I can find 64bit sources?
@kinghunki Can you provide me original english xml? I want to translate it into polish
en.xml
Skorupa123 said:
Hi, where I can find 64bit sources?
@kinghunki Can you provide me original english xml? I want to translate it into polish
Click to expand...
Click to collapse
Here are en.xml
Skorupa123 said:
Hi, where I can find 64bit sources?
@kinghunki Can you provide me original english xml? I want to translate it into polish
Click to expand...
Click to collapse
No 64bit sources. HTC push OTA's but not release sources on htcdev.com, what is very unusual as GPL say that they MUST to release sources. Nevermind, We can handle that part soon with reverse engineering.
Only what is, let say, close to a51 Qualcomm hardware is sources for Desire 826 (a52) but with lots of changes and patches.
Thank You, tested on A51_UL EU. Works great!
kinghunki said:
Htc_a51dtul test is normal, but still the same problem, choose to "reboot to recovery" will be Repeated restart to recovery!
Click to expand...
Click to collapse
Ya, thank You for that, but I think that here is not problem with device but with twrp.
I can fix that problem but I am not maintainer of omnirom, so not My or Your problem.
If anyone have a time and wish, can participate in omnirom gerrit
Qoneek said:
Thank You, tested on A51_UL EU. Works great!
Click to expand...
Click to collapse
can you please tell if it solves the recovery problem as mentioned here? this problem is driving me crazy...
erany1 said:
can you please tell if it solves the recovery problem as mentioned here? this problem is driving me crazy...
Click to expand...
Click to collapse
What problem You have with recovery? This replace original HTC recovery and You can root, change OS etc..
fergy said:
Hello
Here is attached link to TWRP 2.8.7.0 for Qualcomm's version of 64bit htc_a51ul and htc_a51tuhl. Not sure if it will work with htc_a51dtul (dual sim version for India/Asia) but if someone want to test, please do.
To flash phone, use below fastboot as HTC was change version for 64bit bootloader, so if You use Linux on Your PC, get My version, put together with recovery.img in same folder, restart phone into bootloader and execute:
Code:
chmod 755 fastboot
Code:
./fastboot flash recovery recovery.img
NOTE that dot and slash are IMPORTANT. If You skip it, will not use My fastboot but other which probably not work and You will get error flashing.
If You are on windows, please use latest version of fastboot for windows.
As usual, TRWP sources are on Omnirom github, device sources are on My github.
NOTE THAT YOU NEED TO HAVE 64bit BOOTLOADER (Lollipop installed on device)
Happy rooting
CAUTION: I am not responsible if You delete and/or brick Your device!!!
DOWNLOAD
EDIT1: attach removed due to bug inside. Will attach new one asap fix bug and recompile.
EDIT2: attach attached back
Click to expand...
Click to collapse
Hello.
I tried once to change my stock recovery img but I ended up with a non compatible one and it has been impossible to find a good one.
I can only use my PC and ADB to flash one.
I'm using windows 10 and this model htc_a51tuhl. I have ADB and everything installed.
When i try to flash the recovery you posted: CMD "fastboot flash recovery recovery.img", it says "invalid sparse file format". I assume that the file is too big, but why?
Isn't it supposed to work? or it's only for linux users? Can someone inlight me please.
I'm struggling to find a working recovery to root my phone and so if someone share a working one for me, that would be very very nice.