Related
Tried SAUROM, experiencing quite worse connectivity, esp. when switching between LTE and 4G. Would prefer to go back to complete stock, like the AT&T Odin-flashable tar that Da_G posted here but for Telus instead.
I have CWM and Odin so I don't believe format is an issue (img/tar/zip)
Can anyone help?
*Bump*
I too request the stock Telus Galaxy Note Firmware... If anyone can dump it, please do so!
I would also like Telus stock rom if possible.
Thanks.
If anyone is running stock Telus and is willing to do a dump, I'm sure me or anyone else here asking for this would be more than willing to type up instructions/guide you through the process of dumping the stock stuff!
I have the stock rom but its rooted with dag. Then reflashed back to stock kernel, and it kept the root.let me know if i can help and how
Sent from my SGH-I717D using XDA
I just got my Galaxy Note from TELUS, yesterday.
If you tell me how to do it, I will.
Also, check out the reset counter thread in the dev section. You can help us out there aswell they want a telus phone with 0 flash count to pull the code block
Sent from my SGH-I717D using XDA
crielstar said:
Also, check out the reset counter thread in the dev section. You can help us out there aswell they want a telus phone with 0 flash count to pull the code block
Sent from my SGH-I717D using XDA
Click to expand...
Click to collapse
I sent a PM to braway about that, waiting for him to reply.
That is great news your the man! If u get that stock rom/kernal/radio and counter reset going our telus notes can start see decent dev work.rogers and att guys are leavin us in the dust!
Sent from my SGH-I717D using XDA
sadly, as I wrote to Jckpsa already,
you can only do one of the two things.
either dump system, or get the data for the flash counter reset.
unless there is a way to dump the system image, that does not require root...
crielstar said:
I have the stock rom but its rooted with dag. Then reflashed back to stock kernel, and it kept the root.let me know if i can help and how
Sent from my SGH-I717D using XDA
Click to expand...
Click to collapse
Jckpsa said:
I just got my Galaxy Note from TELUS, yesterday.
If you tell me how to do it, I will.
Click to expand...
Click to collapse
Wouldn't the best solution be for you to dump the stock rom/kernel/recovery while jckpsa pulls the flash counter reset?
I did "adb pull /system"
and I got these:
folders:
app, bin, csc, etc, fonts, framework, hdic, lib, media, T9DB, tts, usr, vsc, xbin
files:
build.prop, CSCFiles.txt, CSCVersion.txt, SW_Configuration.xml
770MB total, 1,339 files.
And there is a stock TELUS kernel in the Android-Development section.
I can upload those system folders/files if that will help.
bump.
I really need a stock odin or system because somehow I managed to forget to make a backup and I need to exchange my phone...
Jckpsa said:
I did "adb pull /system"
and I got these:
folders:
app, bin, csc, etc, fonts, framework, hdic, lib, media, T9DB, tts, usr, vsc, xbin
files:
build.prop, CSCFiles.txt, CSCVersion.txt, SW_Configuration.xml
770MB total, 1,339 files.
And there is a stock TELUS kernel in the Android-Development section.
I can upload those system folders/files if that will help.
Click to expand...
Click to collapse
As far as I know, you need to input this code:
c:\> adb shell
$ su
# dd if=/dev/block/mmcblk0p24 of=/sdcard/system.img
# dd if=/dev/block/mmcblk0p22 of=/sdcard/recovery.img
# dd if=/dev/block/mmcblk0p8 of=/sdcard/boot.img
# exit
c:\> adb pull /sdcard/system.img
c:\> adb pull /sdcard/recovery.img
c:\> adb pull /sdcard/boot.img
From there, we just need to be able to make it an Odin-flashable tar file. I'm not quite sure of those specifics, can somebody else pull through here?
Okay if a stock image isn't posted up in time, am I going to get hassled if I am within my first 30 days and instead put the phone into a bootloop so TELUS cannot see that I've modified it (unless they go into recovery or download mode eep)? I really wouldn't like to do this if possible but if I do, I'll have a stock telus note and will upload the rom
smurcoch said:
Okay if a stock image isn't posted up in time, am I going to get hassled if I am within my first 30 days and instead put the phone into a bootloop so TELUS cannot see that I've modified it (unless they go into recovery or download mode eep)? I really wouldn't like to do this if possible but if I do, I'll have a stock telus note and will upload the rom
Click to expand...
Click to collapse
I say try, bootloop should throw them off
I think I would need to root my phone to pull those dds.
Glad to help if I can but my phone is unrooted... Let me know.
That's quite the dilemma if true - how does one pull if adb su requires root?
edit: disregard the below because I realized the thread is also about having the stock recovery.
Doesn't one just flash Clockworkmod through ODIN and then perform a completely stock nandroid backup
This is the point where one would then flash the rooted kernel and/or ROM. I was positive that I did a backup before flashing the root kernel but I believe I was a little too excited
Anyone with a new Telus Galaxy Note that is untouched should reply to this thread so we can get a stock img of our device.
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Flash kdz then install cwm then backup the stock ROM THEN do your mods. Every time every phone. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Yes, offline flash the kdz. Always backup your rom whenever you so something like that.
Sent from my LG-P769 using Tapatalk 4
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
kuma82 said:
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
Click to expand...
Click to collapse
Get outta here kuma, no one wants you here. -___- lol im jk.
Sent from my LG-P769 using Tapatalk 4
Lol, okay
NOT!
CM 10.1 P769
kuma82 said:
Lol, okay
NOT!
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
What variant do you have 769? Flash recovery.img in fastboot.
Sent from my LG-P769 using Tapatalk 4
swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
Sorry I didn't break it down enough for you. You have to get fastboot up and running. Jellybean does not operate when starting in S/W mode, that's why you get the connection problem. Now ice cream, does operate when starting in the S/W upgrade mode. With fastboot you can flash everything you need to get the offline flash working. These three links are all the info you need.
Lelus fastboot
Select the option to flash x & u for p769
1. http://forum.xda-developers.com/showthread.php?p=41768774
Help if you can't get fastboot installed
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
Info on how to use fastboot manually. Not really needed because lelus has everything needed in the first link.
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sorry I told you flashing the boot.IMG will help(was thinking of default.prop), I just remembered the build.prop is in the system partition.
CM 10.1 P769
---------- Post added at 11:00 PM ---------- Previous post was at 10:52 PM ----------
Lelus said:
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
Click to expand...
Click to collapse
Thanks for sharing, I didn't know stock recovery allowed ADB commands :thumbup:
CM 10.1 P769
swm5126 said:
Hi,
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Factory LG mobile support tool has an option to "update recovery" in top right menu. This will download latest factory rom via internet and reflash phone in software update mode to reset everything.
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Works well.
might have to set phone into software update mode by pressing vol up and then inserting usb cable..
kuma82 said:
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Click to expand...
Click to collapse
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
swm5126 said:
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
Click to expand...
Click to collapse
Just kidding, got it figured out. Flashed the ICS xloader. Looks like its letting me restore finally! Thanks!
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Thank you! I'll update my guides now you made some folks very happy today.
Sent from my VS980 4G using Tapatalk 4
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
WACOMalt said:
Phew, you were one of the guys I was worried about who were unlucky enough to be stuck in boot loop WITHOUT adb. Glad he got you working again!
Click to expand...
Click to collapse
I am too LOL Thanks for all your help
I had nothing to do with it, all thanks go to thecubed/IOMonster
Sent from my VS980 4G using Tapatalk 4
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
jspradling7 said:
Cool! :victory:
Glad to see you have yours working. I left mine at home today and brought the S4 instead so I'll fix my G2 tonight. Thanks for the help everyone!
Click to expand...
Click to collapse
Yeah that's what I did yesterday as well used my s4 glad I didn't sell it yet
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
I could swear I said just nuke the FOTA partition sometime yesterday as usual awesome job.
thecubed said:
Howdy all!
Did you install TWRP and then take the OTA, now you can't get your phone to boot normally, but you do see TWRP?
Here's the easy fix:
If you have ADB access, plug in your phone and run this:
Code:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!
Let me know if this helps anyone!
As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can.
Click to expand...
Click to collapse
Thank you!! Where do I send the beer money?
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
Click to expand...
Click to collapse
Nevermind I found it, not used terminal before in recovery, phone back up and running
jbreaz said:
THANK YOU THANK YOU THANK YOU this worked perfectly using the method without adb. YES YES YES
Click to expand...
Click to collapse
I was upset yesterday worrying about you guys. I am happy to see you happy. Thanks much OP for the fix.
I am rooted and installed TWRP recovery but reverted back to the stock recovery before accepting the VZW OTA update. I'm now stuck in a boot loop and I can't get ADB to recognize my device when plugged in via USB. When I plug in my phone it shows the following:
Fastboot mode started
udc_start()
-reset-
-portcharge-
-reset-
-portcharge-
fastboot: processing comands
Any idea why this is happening and how I can get my phone to boot normally?
Walter21026 said:
when i hit terminal command it goes to the folder browser is that supposed to happen? how do i bring up the terminal from here? my sideload isnt working like it did once earlier thats why im asking
Edit: My adb sideload def isnt working now if someone can clue me in on how to get to the terminal command in recovery im still seeing the folder browser after I touch the terminal button in recovery
---------- Post added at 09:45 AM ---------- Previous post was at 09:16 AM ----------
Nevermind I found it, not used terminal before in recovery, phone back up and running
Click to expand...
Click to collapse
I too get the file folder. How do i get the terminal command in TWRP?
synplex said:
I too get the file folder. How do i get the terminal command in TWRP?
Click to expand...
Click to collapse
When you see the file folder just ignore that and hit "select "on the bottom right and that will bring it up. Just type the command from there
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
synplex said:
Thanks it worked!:laugh: Should I flash stock now update via OTA then reroot and reflash TWRP??
Click to expand...
Click to collapse
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Walter21026 said:
I didn't. From what I've read its just best to flash the new TWRP and not worry about the new OTA. Besides there is nothing relevant about the OTA enough to worry about going through all the trouble of installing the OTA. Also the devs have pulled all the new update files and they will use those in their Roms
Click to expand...
Click to collapse
Yea, let's just wait for a ROM worth flashing and "F OTA"
How can we get the OTA if we have TWRP installed?
Can we falsh stock recovery and then accept the Update?
If so can someone please post the Stock Recovery IMG?
My phone is at the LG screen and the notification light is blinking but thats it. How can I adb anything or get into twrp?
So I picked up this tablet at MicroCenter. Not bad for $40. Not a lot of features, but I knew that going in. Nice that it has 4.2.2 and the Play Store works like it should!
I wanted to start a general thread to keep up to date on any recoveries, fixes or ROM's people come across.
I used this method to root http://www.cydiaimpactor.com/ it worked the first try. I had to do it on an old XP machine because my Windows 8 would not load the right Android drivers. See posts below for another method.
Please post any additional information you may have on this tablet. Let's see if we can make the most out of our $40!
A special thanks to BLuFeNiX for jump starting this whole thread with his knowledge, CWM recovery and stock NANDs, and for taking time to gather all the info into a useful post.
Also thanks to extreme tester dsulliii for the willingness to sacrifice his tablet in the name of science and for all his insight and help.
Don't forget to hit the thanks button for them !!!!!
CWM Recovery, Return To Stock, and More!
My dropbox links keep getting suspended, so here is a media fire link for all my files: https://www.mediafire.com/folder/gm9wb67b05bs4/Azpen_A700
Also, check out the forums at SDX: http://forum.sdx-developers.com/viewforum.php?f=528
ClockworkMod Recovery
Changelog:
Code:
CWM build 5 (2013-12-02)
* corrected internal and external sdcard mount points (previously, the external sdcard was being mounted at /emmc, which is just wrong. The new mount points are /sdcard and /external_sd)
* added more partitions under "mounts and storage" (in case anyone wants to mount them or format them)
CWM build 4 (2013-11-29)
* first working build
Downloads:
CWM build 5 (2013-12-02) Image File | Flashable ZIP
CWM build 4 (2013-11-29) Image File | Flashable ZIP
Stock Recovery Image File | Flashable ZIP
MD5 Hashes:
Code:
73ab81b2e6b1404f1e4e1ed91f32ae7d ./CWM_recovery-Azpen_A700-build-4.img
db028be865f27797bf92cfbd04496101 ./CWM_recovery-Azpen_A700-build-4.zip
8c4ab86c29e83eb9f492623218828142 ./CWM_recovery-Azpen_A700-build-5.img
8e67fa7cb333e242a19306a2859b050c ./CWM_recovery-Azpen_A700-build-5.zip
ff080997ff01838e9d35807e08846724 ./stock_recovery-Azpen_A700.img
816b643ea090b2dd55226b380982c686 ./stock_recovery-Azpen_A700.zip
How to install a flashable ZIP:
Boot into recovery and select "install zip from sdcard." You must be using a custom recovery for this to work (otherwise authentication will fail).
How to install a recovery image:
Copy the image file to your SD card and run the following commands via ADB or a Terminal Emulator:
Code:
su
dd if=/sdcard/name_of_recovery.img of=/dev/block/nandg
sync
You can now reboot into CWM recovery.
Return To Stock ROM
NOTE: These images are not 100% stock because they are fully rooted. If you want true stock, just replace the /system/xbin/su binary with the original, which is preserved as /system/xbin/su.original
The easy way:
I have created an flashable zip to return to stock. You can download it here: Azpen A700 Stock ROM Flashable ZIP
Just copy it to your SD card, boot into CWM, and select "install zip from sdcard." Before rebooting, select "wipe data / factory reset."
The hard way:
Alternatively, stock images for the Azpen A700 can be downloaded here. To return to stock, download the important nand images (a, b, c, d, g) and, copy them to your SD card and then run the following commands via ADB (you must be booted into CWM if you wish to flash anything other than recovery/nandg):
Code:
su
dd if=/external_sd/nanda.img of=/dev/block/nanda
dd if=/external_sd/nandb.img of=/dev/block/nandb
dd if=/external_sd/nandc.img of=/dev/block/nandc
dd if=/external_sd/nandd.img of=/dev/block/nandd
dd if=/external_sd/nandg.img of=/dev/block/nandg
sync
Before rebooting, select "wipe data / factory reset."
Unbricking via Livesuit
First, your device needs to be in FEL mode. There are a few ways to accomplish this:
dsulliii said:
1) Make sure your A700 is turned off. (Do NOT have the micro-USB end plugged into your A700 at this time, that is for later.)
2) Start LiveSuit on your computer. (The COMPUTER end of your USB cable should be plugged into ONLY your computer at this stage.)
3) Select the ROM that you want to flash to your A700.
4) Hold down the Vol button on your device (I usually hold it down Vol-, not Vol+, but I believe that this device does not matter which.)
5) While holding down Vol, plug the micro-USB end of the cable into your A700. Keep holding down the Vol button.
6) While still holding down the Vol button, WITH the USB cable now connected between your computer and your A700, press and release the A700's Power button 10 times, and wait for a second to a few.
7) The LiveSuit program will detect your A700 going into download mode and begin prompting you for what to do.
8) Follow LiveSuit's recommendations, including formatting. It will take less than 5 minutes.
*** IF *** you don't get the LiveSuit prompting after step #6 as described in step #7, it means that you don't have the ADB-USB drivers for the A700 installed into your Windows. The easiest way to do that is to run each of the three other ".exe" driver install programs that are in your LiveSuit directory. ONE of those properly installs the needed driver to make LiveSuit detect your A700. *** EndIF ***
Click to expand...
Click to collapse
You can also get into FEL mode by using a specially formatted SD card. Read about it here: http://linux-sunxi.org/FEL
The file you want to write to the SD card is here: fel-sdboot.sunxi
NOTE 1: Be sure to backup the SD card first, since the data will be gone.
NOTE 2: There is no on-screen indication that your device is in FEL mode. You can tell by plugging the device into your PC and seeing if it is recognized.
Next, flash the livesuit image from here using the Livesuit software. This will install an older version of android on your A700 (a current version image is not yet available). After you unbrick, you can return to stock jellybean 4.2.2 using the instructions found above.
Partition Descriptions
nanda -- bootloader (loads android or recovery and contains boot animation, battery charging images, etc.)
nandb -- env (sets environment variables and helps bootloader)
nandc -- boot (android kernel and ramdisk, this loads on normal boot)
nandd -- system (everything in /system)
nande -- data (everything in /data)
nandf -- misc (used to store temporary data between boot stages and reboots)
nandg -- recovery (recovery kernel and ramdisk)
nandh -- cache (various temporary files)
nandi -- databk (a backup of some of the more important files in /data)
nandj -- sdcard (internal sd card)
Extended Power Menu mod [by ften]
Read the original post here: http://forum.xda-developers.com/showpost.php?p=48225023&postcount=134
Download the flashable zip here: Azpen A700 EPM installer
If you like my work, feel free to donate.
We'll see
After my 1st round of "what's it gonna take to root this". And I do a appreciate a fairly slim JB dist. But I think this lil guy could use a few tweaks here and there.
I'm leaning towards "Kingo Root" for simplicity's sake. Or, "Cydia Impactor" Honestly though, I'm prolly too busy to spend the interrupted time to do a root for a bit. So I'll just check in and see what's up. GMTA ComStart. Thanks!
ranchdude said:
After my 1st round of "what's it gonna take to root this". And I do a appreciate a fairly slim JB dist. But I think this lil guy could use a few tweaks here and there.
I'm leaning towards "Kingo Root" for simplicity's sake. Or, "Cydia Impactor" Honestly though, I'm prolly too busy to spend the interrupted time to do a root for a bit. So I'll just check in and see what's up. GMTA ComStart. Thanks!
Click to expand...
Click to collapse
Well, the device is already rooted over ADB. You just need to shell in and replace the su binary with one that doesn't restrict user apps from gaining root.
Getting back to stock
I'm a neophyte, so I bought this one knowing that if I broke it (which I most likely would -- and did), then I wouldn't be out a whole lot of money. My experiences in learning so far with these A13s is that they're practically un-brickable... once you ruin them, there always seems to be a way to get back on track. So after messing this one up, I was again surprised that all was not lost. I found an ICS ROM that did install using LiveSuit, and it's back up and running again. Only problem is... it was a very nice, slick little JellyBean 4.2 machine before I messed it up. I'd love to get it back to where it was before I messed it up (like I've been able to with other A13s), but ran into an unexpected impasse... CWM Recovery.
The way I got back to installed-version before was by installing a workable ROM then using CWM Recovery to copy ROM-dump files that I pulled prior to messing around back into it. Well, unbeknownst to me, THIS one doesn't have a CWM Recovery yet. And developing one is way beyond my abilities at this point... I am totally relying on you-all with way-more experience than me.
When I went to the Azpen support site, the only ROM they have is allegedly an A700/A701. THAT one doesn't flash using LiveSuit. It errors out at the beginning. So I'm guessing that Azpen support isn't up-to-date yet. I wrote to them, but haven't heard back. I really want to be able to reset it back to its original flashed ROM. Without CWM Recovery, my expected plan for restoration kind of croaked.
So here's my question.... do any of you know of an original ROM that I can get my mitts on that WILL indeed flash to this Azpen A700? I'd love to get its original JellyBean 4.2 working on it again. PLUS... the ICS ROM that DID work in it makes it a different signature... I want it to be an Azpen A700 again.
I know... asking lots and contributing nothing. I'd be thrilled to help anybody gain the same victory that I did with the Mach Speed Trio Stealth 7c A13b if they're having trouble -- in return. Just a hobby of mine, but I hope to someday be good like ya'll.
David
dsulliii said:
So here's my question.... do any of you know of an original ROM that I can get my mitts on that WILL indeed flash to this Azpen A700? I'd love to get its original JellyBean 4.2 working on it again. PLUS... the ICS ROM that DID work in it makes it a different signature... I want it to be an Azpen A700 again.
David
Click to expand...
Click to collapse
I can send you a CWM build that might work. I've been working on one. I make no promises though. My last 2 builds bricked and I had to return the tablet for a new one. I suppose you won't be in any worse of a place though, since you found a working livesuit image. Can you send me a link to the livesuit image? I haven't found a working one yet.
So, let me know if you want me to send my possibly-working CWM build.
BLuFeNiX said:
I can send you a CWM build that might work. I've been working on one. I make no promises though. My last 2 builds bricked and I had to return the tablet for a new one. I suppose you won't be in any worse of a place though, since you found a working livesuit image. Can you send me a link to the livesuit image? I haven't found a working one yet.
So, let me know if you want me to send my possibly-working CWM build.
Click to expand...
Click to collapse
Ya know what, BluFeNiX? I think that would be wonderful. I'm a perfect "test" person for you because I can put mine back the way it is. I'd love to be instrumental in helping to get a CWM working for it.
I don't know HOW you would send it to me though. All I've ever observed here is links within posts. Is that what you would do? Or do you need an e-mail address or something? I'm pretty thrilled to give 'er a try!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:25 PM ----------
PS -- as soon as I re-find that link, I'll post it for you.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
---------- Post added at 08:17 PM ---------- Previous post was at 07:43 PM ----------
dsulliii said:
Ya know what, BluFeNiX? I think that would be wonderful. I'm a perfect "test" person for you because I can put mine back the way it is. I'd love to be instrumental in helping to get a CWM working for it.
I don't know HOW you would send it to me though. All I've ever observed here is links within posts. Is that what you would do? Or do you need an e-mail address or something? I'm pretty thrilled to give 'er a try!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
---------- Post added at 07:43 PM ---------- Previous post was at 07:25 PM ----------
PS -- as soon as I re-find that link, I'll post it for you.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
_______________________________________________________________________________
Okay, I found it at:
(Just discovered that I'm not experienced on the site enough to post links yet.)
It's on a dot-com site called moveontechnology, and it's by hugoenchina with a page id of 220. It's in Spanish.
Maybe you can use some of this info to locate it on Google Search since I can't post the link.
(I used Google Chrome so that I could translate the page from Spanish to English)
Then find the section just a little down the page:
************************************************** **
TABLETS FIRMWARES A13 CPU BOARD BEGINS WITH INET XXX, eg Inet 86vs
(A13) (86VS-M758C1) (CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480) (BLOGHUGOENCHINA) 20130725. Zip "inform me also works in denver electronics TAC-70051" and the Mitsui model MID7104SC
Although the ICS ROM above works, do NOT use it. It incorrectly partitions the device
(A13) (86V-M758B) (CPT-FTG700D3-50PIN-800X480) (TOUCH-NOPLANO) (BLOGHUGOENCHINA) 20130725. Zip
(A13) (86V-M729) (CPT-LT70009-40PIN-800X480) (BLOGHUGOENCHINA) 20130725.zip
(A13) (86V-M758A) (CPT-FTG700D3-50PIN-800X480) (TOUCH-UP) (BLOGHUGOENCHINA) 20130725.zip
************************************************** **
As you can see, I downloaded the first one. I don't know whether the other three work or not because this one works great, although it's ICS.
If you click on that first one, it will give you another link that I can't post on depositfiles.
The actual file is mus464gwg.
Then using Azpen's LiveSuit A701.exe, after extracting the "img" out of the "zip", this "img" works.
Although the ICS ROM below works, do NOT use it. It incorrectly partitions the device
(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.zip
(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img
BLuFeNiX said:
I have started investigating how to create a CWM recovery for this device. All the information I currently have is in my reddit thread (which I cannot link due to my low post count). The title is "Can anyone help me build a CWM recovery for the Azpen A700 tablet? (work I've already done and details inside)"
If anyone has any info that may help me in this endeavor, please message me here or on reddit.
EDIT: How can we get a sub-forum started for this device?
Click to expand...
Click to collapse
I just read through your reddit thread here http://www.reddit.com/r/androiddev/comments/1qt0tk/can_anyone_help_me_build_a_cwm_recovery_for_the/ - great job! Looks like you are making some progress. I also saw the cyanogen thread where the guy took his tablet apart to take some pictures. Can't miss the big Allwinner A13 chip.
Sent from my A700 using XDA Premium 4 mobile app
dsulliii said:
Ya know what, BluFeNiX? I think that would be wonderful. I'm a perfect "test" person for you because I can put mine back the way it is. I'd love to be instrumental in helping to get a CWM working for it.
I don't know HOW you would send it to me though. All I've ever observed here is links within posts. Is that what you would do? Or do you need an e-mail address or something? I'm pretty thrilled to give 'er a try!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Great, thanks for testing for me! Here are the links:
CWM build 1
CWM build 2
I have included 2 builds for you to test. They both contain the same software, but I packaged them slightly differently. I'm pretty new to building stuff for android devices, so I might need a few tries before I make a successful build. Try #1 first by booting into recovery and selecting "install zip fro SD card" or something like that. If #1 doesn't work, try #2 and let me know which one worked.
If anything isn't clear, let me know and I can explain further. Thank you so much for testing for me!
CWM build 1
BLuFeNiX said:
Great, thanks for testing for me! Here are the links:
<<snipped the links>>
I have included 2 builds for you to test. They both contain the same software, but I packaged them slightly differently. I'm pretty new to building stuff for android devices, so I might need a few tries before I make a successful build. Try #1 first by booting into recovery and selecting "install zip fro SD card" or something like that. If #1 doesn't work, try #2 and let me know which one worked.
If anything isn't clear, let me know and I can explain further. Thank you so much for testing for me!
Click to expand...
Click to collapse
__________________________________________________________________
Currently running the (A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img ROM on Azpen A700.
1) Currently running actively from the desktop and selecting SystemSettings-->Backup&Reset-->RecoveryMode-->Ok. (Wait for shutdown & restart)
2) Started into "Android system recovery <3e>". Where "Android system recovery utility (EVB: vol up/vol down, home, enter)" prompt has following options:
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
3) Had copied cwm6028-a700-text.zip to internal SD card, and it does indeed list in "apply update from external storage". Seems that some folks should get some consistency between the meaning of "internal" and "external". But that's neither here nor there. So I am selecting your zip file after volume-downing to it and pressing the power button to select...
RESULTS:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
4) So now i will "reboot system now" and ensure that nothing detrimental occurred....
YEP -- No problem! Device still not bricked, so that's good for me.
The ball's still in your court on this one (that was still fun, nevertheless, thanks.)
-- David
---------- Post added at 09:00 AM ---------- Previous post was at 08:47 AM ----------
BLuFeNiX said:
Great, thanks for testing for me! Here are the links:
<<links snipped>>
I have included 2 builds for you to test. They both contain the same software, but I packaged them slightly differently. I'm pretty new to building stuff for android devices, so I might need a few tries before I make a successful build. Try #1 first by booting into recovery and selecting "install zip fro SD card" or something like that. If #1 doesn't work, try #2 and let me know which one worked.
If anything isn't clear, let me know and I can explain further. Thank you so much for testing for me!
Click to expand...
Click to collapse
_________________________
Title: CWM build 2
Everything same as before, but this time it is "cwm6028-a700-test2.zip" that I have selected to install.
Results:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
(Still exciting though... getting to watch the status bar increase to about 5% before failing.)
Looking forward to the next hurdle. COOL!
dsulliii said:
RESULTS:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
(Still exciting though... getting to watch the status bar increase to about 5% before failing.)
Looking forward to the next hurdle. COOL!
Click to expand...
Click to collapse
Ah, okay! I just have to re-sign the zip file. I'll send you some resigned builds shortly.
Happy Thanksgiving
BLuFeNiX said:
Ah, okay! I just have to re-sign the zip file. I'll send you some resigned builds shortly.
Click to expand...
Click to collapse
Excited to try it again. But the wife and I are about to take off across town to the oldest son's home for the Holiday feast. I may-or-may-not get to it before the day is out, but I'm going to be chomping at the bit to get home and give it another try. It's 11:30am here (Mountain time). Later, thanks, and Happy Thanksgiving!
dsulliii said:
Excited to try it again. But the wife and I are about to take off across town to the oldest son's home for the Holiday feast. I may-or-may-not get to it before the day is out, but I'm going to be chomping at the bit to get home and give it another try. It's 11:30am here (Mountain time). Later, thanks, and Happy Thanksgiving!
Click to expand...
Click to collapse
Hey, no problem. Have a happy Thanksgiving! Here are the new (hopefully correctly-signed) zips:
Signed zip test 1
Signed zip test 2
Looking forward to hearing the results!
Hey BLuFeNiX, I was fortunate to connect to xda on my son's wi-fi and download your new ones. They both failed signature verification again. He's interested as well, so we can probably keep plugging away at this through the day. -- David
Sent from my M758C1 using Tapatalk
dsulliii said:
Hey BLuFeNiX, I was fortunate to connect to xda on my son's wi-fi and download your new ones. They both failed signature verification again. He's interested as well, so we can probably keep plugging away at this through the day. -- David
Sent from my M758C1 using Tapatalk
Click to expand...
Click to collapse
Okay. Let's try this a different way. Is your tablet rooted? if so, please install Android Terminal Emulator from the Play Store.
Also, copy these img files to your internal sdcard:
Image test 1
Image test 2
Open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/recovery-TEST.img of=/dev/block/nandg
sync
reboot recovery
This will flash the recovery directly from Android instead of having to boot into recovery. If the first one doesn't work, you can try the second one. If we are successful, you should boot into CWM. If not, you'll probably need to flash using livesuit again.
If you are not rooted (you will get an error when you use the "su" command), let me know and I will tell you how to obtain root.
Good luck, and thanks again!
Yep, rooted, su worked okay in terminal, got the #.
Dowloaded okay, will try the dd flash. If it doesn't work and I have to reflash, won't be able to let you know until I get home tonight.
Sent from my M758C1 using Tapatalk
---------- Post added at 04:32 PM ---------- Previous post was at 03:39 PM ----------
Forgot my cell phone had Tap-a-talk on my cell phone. Interesting... reboot recovery from terminal rebooted system, but not recovery. So used settings app to reboot into recovery. When I did that, I got little colorful Andy who just stayed there and never went into recovery nor system. Forced a shutoff using the power button. Turned on... same freeze point. Forced power off again and tried to start recovery with volume and power. Same no-go. Only could try the first img since it's stuck. Will now have to wait till we get home then I"ll flash the ICS ROM and try your second img.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
ADDENDUM: The problem that I had with not rebooting recovery from a shell command has gone away. I suspect that it might have something to do with the ICS ROM that I was using partitioning the device wrong. Make sure you use BLuFeNiX's modified ROM for proper A700 partitioning, and NOT the one that I recommended earlier in the thread.
dsulliii said:
Yep, rooted, su worked okay in terminal, got the #.
Dowloaded okay, will try the dd flash. If ut doesn't work and I hace to reflash, won't be able to let you know until I get home tonight.
Sent from my M758C1 using Tapatalk
---------- Post added at 04:32 PM ---------- Previous post was at 03:39 PM ----------
Forgot my cell phone had Tap-a-talk on my cell phone. Interesting... reboot recovery from terminal rebooted system, but recovery. Do used settings app to reboot into recovery. When I did that, I got little colorful Andy who just stayed there and never went into recovery nor system. Forced a shutoff using the power button. Turned on... same freeze point. Forced power off again and tried to start recovery with volume and power. Same no-go. Only could try the first img since it's stuck. Will now have to wait till we get home then I"ll flash the ICS ROM and try your second img.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Interesting results. The second image loads the ramdisk from a different memory address, so hopefully the behavior you saw was what happens when an incorrect memory address is used. Maybe #2 is the correct one
Thanks again for doing all this testing.
Just looked over my posts from earlier. So VERY sorry about the spelling errors! I wasn't looking back to see the mis-predictions. I hate it when people do that. Anyway, on my way home now. Should be able to let you know about the second img in about an hour. (8:00pm mountain time).
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Image test 2
BLuFeNiX said:
Okay. Let's try this a different way. Is your tablet rooted? if so, please install Android Terminal Emulator from the Play Store.
Also, copy these img files to your internal sdcard:
<<links snipped>>
Open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/recovery-TEST.img of=/dev/block/nandg
sync
reboot recovery
This will flash the recovery directly from Android instead of having to boot into recovery. If the first one doesn't work, you can try the second one. If we are successful, you should boot into CWM. If not, you'll probably need to flash using livesuit again.
If you are not rooted (you will get an error when you use the "su" command), let me know and I will tell you how to obtain root.
Good luck, and thanks again!
Click to expand...
Click to collapse
_____________
Okay, I'm home now.
Before getting started, I restarted the A700 using the power button. It (again) did not progress beyond the teensy colorful Andy.
So I connected my USB cable to the computer and tried to ADB it.... ADB did not see it. I predicted it did not get any farther, but I just wanted to make sure and to let you know as well.
So I used LiveSuit A701.exe to flash the ICS "(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img" ROM again ... complete success as always.
After it powered up to the ICS desktop, I "ADB devices" which resulted positive. Followed by "ADB shell" whereupon I got the "#" indicating that this ROM comes rooted, it started in as superuser.
I copied your "recovery-TEST2.img" to the internal SDcard.
Went back into ADB Shell and at the # prompt typed:
su ' superfluous since already superuser
dd if=/sdcard/recovery-TEST2.img of=/dev/block/nandg
sync
reboot recovery
Again, the shell "reboot recovery" command did not reboot the recovery partition... it rebooted the system partition back into my ICS desktop.
So again I SystemSettings->Backup&Reset->RecoveryMode->Ok. And waited for it to power off and restart.
I got the small colorful Andy.... forever.... and again no sign of any additional advancing.
Still had the USB cable plugged in, so tried ADB devices again while it was sitting on Andy. No good, no ADB running.
Used the power button to force a power off.
After it powered off, waiting 30 seconds, I used the power button to turn it back on.
It displayed the colorful little Andy.... and didn't go anywhere still.
So I will re-flash the ICS ROM and wait for you to find some more magic.
Yeah, this is fun. THANKS BLuFeNiX. :good:
---------- Post added at 08:47 PM ---------- Previous post was at 08:15 PM ----------
More experimentation. I installed Uberizer's tollkit to have it perform the reboot into recovery. Identical to the shell's reboot recovery, it also reboots into the system. It appears that this ROM and the Azpen JellyBean 4.2 ROM must know something special about this tablet, eh?
Sent from my M758C1 using Tapatalk
ADDENDUM: The "reboot recovery" issue from a shell command has gone away. I believe that it was most likely caused by the ICS ROM that I was flashing -- having the device partitioned incorrectly.
dsulliii said:
_____________
Okay, I'm home now.
Before getting started, I restarted the A700 using the power button. It (again) did not progress beyond the teensy colorful Andy.
So I connected my USB cable to the computer and tried to ADB it.... ADB did not see it. I predicted it did not get any farther, but I just wanted to make sure and to let you know as well.
So I used LiveSuit A701.exe to flash the ICS "(A13)(86VS-M758C1)(CPT-OR-SKYRAINBOW-H070D-12AY-50PIN-800X480)(BLOGHUGOENCHINA).20130725.img" ROM again ... complete success as always.
After it powered up to the ICS desktop, I "ADB devices" which resulted positive. Followed by "ADB shell" whereupon I got the "#" indicating that this ROM comes rooted, it started in as superuser.
I copied your "recovery-TEST2.img" to the internal SDcard.
Went back into ADB Shell and at the # prompt typed:
su ' superfluous since already superuser
dd if=/sdcard/recovery-TEST2.img of=/dev/block/nandg
sync
reboot recovery
Again, the shell "reboot recovery" command did not reboot the recovery partition... it rebooted the system partition back into my ICS desktop.
So again I SystemSettings->Backup&Reset->RecoveryMode->Ok. And waited for it to power off and restart.
I got the small colorful Andy.... forever.... and again no sign of any additional advancing.
Still had the USB cable plugged in, so tried ADB devices again while it was sitting on Andy. No good, no ADB running.
Used the power button to force a power off.
After it powered off, waiting 30 seconds, I used the power button to turn it back on.
It displayed the colorful little Andy.... and didn't go anywhere still.
So I will re-flash the ICS ROM and wait for you to find some more magic.
Yeah, this is fun. THANKS BLuFeNiX. :good:
---------- Post added at 08:47 PM ---------- Previous post was at 08:15 PM ----------
More experimentation. I installed Uberizer's tollkit to have it perform the reboot into recovery. Identical to the shell's reboot recovery, it also reboots into the system. It appears that this ROM and the Azpen JellyBean 4.2 ROM must know something special about this tablet, eh?
Sent from my M758C1 using Tapatalk
Click to expand...
Click to collapse
Alright, I am starting to run out of ideas. Try this build (use the dd method again):
CWM recovery test 3
If this one doesn't work, I'll need to spend some more time doing research. Thanks and good luck!
I have an LG Optimus Fuel (LG L34C) from Straightalk running Android 4.4. This phone is (as far as I know) the same as the LG Optimus Zone 2 from Verizon Prepaid.
I couldn't find a halfway decent manual for the LG L34C so I followed the LG Optimus Zone 2 Manual to enter Recovery mode. When I held the buttons on the L34C, it would boot, show the LG logo, then shut off, show the LG logo, and do it again. As long as the buttons were held in would loop.
So I downloaded the ADB and tried to do it from there.
"adb reboot recovery" brings up the classic "No Command".
"adb reboot bootloader" just reboots it.
"adb reboot download" just reboots it.
"adb reboot fastboot" just reboots it.
What the heck is going on! I'm going crazy trying to figure this out. Why can't I access any of the special menus?
Oh, and TowelRoot didn't work to root the phone either.
I tried to enter Recovery Mode on my Nexus 7 (2012) and noticed that I also get the "No Command" prompt. I was then able to hold 'Power' and press 'Volume Up' to enter Recovery mode.
I tried this, and every other imaginable button combination, on the LG Optimus Fuel and had no luck whatsoever.
Is it possible that this stuff has been disabled by LG?
vwnut13 said:
I tried to enter Recovery Mode on my Nexus 7 (2012) and noticed that I also get the "No Command" prompt. I was then able to hold 'Power' and press 'Volume Up' to enter Recovery mode.
I tried this, and every other imaginable button combination, on the LG Optimus Fuel and had no luck whatsoever.
Is it possible that this stuff has been disabled by LG?
Click to expand...
Click to collapse
I to have same prob with it seems factory reset is done thru safemode We need the firmware to get somewhere
toxinburn said:
I to have same prob with it seems factory reset is done thru safemode We need the firmware to get somewhere
Click to expand...
Click to collapse
Is your device activated. Straight Talk said that reset via recovery (it's in the phones manual...) would work after activated, but that seems like BS.
full user guide from LG
Okay I got the full user guide that was NOT included this is the LG Full guide. Just Click it, had to put it on 4shared as it is too large to upload as .pdf on here.
Root worked for me after I followed this guide. http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/ Make sure you change the values in post #1, and remounting /system as explained in reply #1.
vwnut13 said:
I have an LG Optimus Fuel (LG L34C) from Straightalk running Android 4.4. This phone is (as far as I know) the same as the LG Optimus Zone 2 from Verizon Prepaid.
I couldn't find a halfway decent manual for the LG L34C so I followed the LG Optimus Zone 2 Manual to enter Recovery mode. When I held the buttons on the L34C, it would boot, show the LG logo, then shut off, show the LG logo, and do it again. As long as the buttons were held in would loop.
So I downloaded the ADB and tried to do it from there.
"adb reboot recovery" brings up the classic "No Command".
"adb reboot bootloader" just reboots it.
"adb reboot download" just reboots it.
"adb reboot fastboot" just reboots it.
What the heck is going on! I'm going crazy trying to figure this out. Why can't I access any of the special menus?
Oh, and TowelRoot didn't work to root the phone either.
Click to expand...
Click to collapse
i don't know what the heck i did but i got into the recovery. problem is i bricked my device and i need firmware lol. anyone been able to get the OTA firmware zip? if so i need it like,really bad. what i did was i just held down pwr and vol- for like 4 reboots and let go of the power button and then it vibrated twice and i was suddenly somehow in?
---------- Post added at 07:51 AM ---------- Previous post was at 07:46 AM ----------
yackaro said:
i don't know what the heck i did but i got into the recovery. problem is i bricked my device and i need firmware lol. anyone been able to get the OTA firmware zip? if so i need it like,really bad. what i did was i just held down pwr and vol- for like 4 reboots and let go of the power button and then it vibrated twice and i was suddenly somehow in?
Click to expand...
Click to collapse
now that i think about it my device was bricked.... maybe this is a special recovery designed to act only when problems are detected in the boot sequence?
Well, looks like I'm in the same boat now, lol. Going against everything I've learned in the 5 years messing with Android, I had a non-thinking DOH! moment and changed the screen density. After reboot, I just have a bootlooping cheap paperweight for the time being. I can get into recovery, but there's no menu options. I am going to try to push the backed-up build.prop.
They really have this one locked down. I haven't found an OTA zip in my searches yackaro, but I'll keep an eye out for you.
root for lg fule kinda works
I got an lg fule from walmart and decided to root it(never done it befor on any thing)I tried for at least 6 hrs and tied poot z4 all kinds of apks and finely I get towelroot to work but I cant get full acces its says setuid attribute is NOT present BUT root user ownership is present. root access is NOT correctly configured for this file! what is wrong and what do I need to do? I have been using the phone for a week downloading apps from blackmarket and googls app sometimes its kinda slow but It wont let me move systems apps to sd,can delet but not movei have titanium bu supersu busybox pro force2sd esfx and rommaneger how or can I gain full root for kitkat 4.4 lg fuel?
It is possible that TracFone (StraightTalk is a subsidiary of TracFone) is using special bootloader code to lock users out of recovery mode. I know that T-Mobile did something like that with some lower-to-mid-range LG phones.
ColtonDRG said:
It is possible that TracFone (StraightTalk is a subsidiary of TracFone) is using special bootloader code to lock users out of recovery mode. I know that T-Mobile did something like that with some lower-to-mid-range LG phones.
Click to expand...
Click to collapse
I can't (well, couldn't - I'm soft bricked right now) even boot into bootloader. To get full root, I think we need an unlocked boot loader. However, "ADB reboot bootloader" doesn't work, right now, as well as most of all the other commands.
I was able to reboot into recovery, but there wasn't any text. I'm working on getting the fuel booting again, but I haven't found anything that works yet. The hard key combo that LG describes to hard reset doesn't work. And I've tried many other hard key combinations, but nothing works so far. [emoji20]
skyline247 said:
I can't (well, couldn't - I'm soft bricked right now) even boot into bootloader. To get full root, I think we need an unlocked boot loader. However, "ADB reboot bootloader" doesn't work, right now, as well as most of all the other commands.
I was able to reboot into recovery, but there wasn't any text. I'm working on getting the fuel booting again, but I haven't found anything that works yet. The hard key combo that LG describes to hard reset doesn't work. And I've tried many other hard key combinations, but nothing works so far. [emoji20]
Click to expand...
Click to collapse
Yes, what I meant is they might be blocking both recovery, and boot loader mode...
Sent from my HTC One (M8)
ColtonDRG said:
Yes, what I meant is they might be blocking both recovery, and boot loader mode...
Sent from my HTC One (M8)
Click to expand...
Click to collapse
True. They probably are. I don't know why they would block at least hard factory reset, though. But then again, since we paid for our device (albeit only $30) seems like we could have more freedom with it. Oh well.
LG has fastboot locked out. I was browsing the LG G2 forums when I found that people are able to get to fastboot by zeroing out their 'laf' partition and forcing the phone into fastboot (because aboot can't find it) where we can then flash a custom recovery.img hopefully. I have the recovery partition extracted and replaced /sbin/recovery with CWM and repacked. I just need to get into fastboot to test it. I will get a second phone from walmart to dev with, they're only $30. if anyone has a dev phone to test it on, read on...
This is theory and hasen't been tested. We may not even be able to run custom recovery or fastboot.
If anyone wants to pick up here be sure you have fastboot and adb installed and have some dev knowledge, not for noobs like me.
backup your laf partition to an external SD card (insert a micro SD)
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/laf.img
pull laf.img to your computer as a backup and to use later in fastboot
wipe your laf partition [I AM NOT RESPONSIBLE IF YOU KILL YOUR PHONE]
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
reboot your phone and connect it to your computer.
your phone SHOULD (I have not tested this) boot into fastboot as a failsafe.
on your computer
Code:
fastboot flash laf laf.img
Code:
fastboot reboot
phone should reboot back to normal.
This will test that we can in fact get to fastboot.
STOCK laf, boot & recovery files to look at. The included repacker does not repack the images properly. I use linux tools for repacking.
https://dl.dropboxusercontent.com/u/14669363/LGL36C.rar
FlyingPoo said:
LG has fastboot locked out. I was browsing the LG G2 forums when I found that people are able to get to fastboot by zeroing out their 'laf' partition and forcing the phone into fastboot (because aboot can't find it) where we can then flash a custom recovery.img hopefully. I have the recovery partition extracted and replaced /sbin/recovery with CWM and repacked. I just need to get into fastboot to test it. I will get a second phone from walmart to dev with, they're only $30. if anyone has a dev phone to test it on, read on...
This is theory and hasen't been tested. We may not even be able to run custom recovery or fastboot.
If anyone wants to pick up here be sure you have fastboot and adb installed and have some dev knowledge, not for noobs like me.
backup your laf partition to an external SD card (insert a micro SD)
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/laf.img
pull laf.img to your computer as a backup and to use later in fastboot
wipe your laf partition [I AM NOT RESPONSIBLE IF YOU KILL YOUR PHONE]
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
reboot your phone and connect it to your computer.
your phone SHOULD (I have not tested this) boot into fastboot as a failsafe.
on your computer
Code:
fastboot flash laf laf.img
Code:
fastboot reboot
phone should reboot back to normal.
This will test that we can in fact get to fastboot.
STOCK laf, boot & recovery files to look at. The included repacker does not repack the images properly. I use linux tools for repacking.
https://dl.dropboxusercontent.com/u/14669363/LGL36C.rar
Click to expand...
Click to collapse
Sounds like we are a little closer, however you can push a .img thru adb already I know some people that did a mako build only problem is it bricked it.
thatguyrightthere said:
I got an lg fule from walmart and decided to root it(never done it befor on any thing)I tried for at least 6 hrs and tied poot z4 all kinds of apks and finely I get towelroot to work but I cant get full acces its says setuid attribute is NOT present BUT root user ownership is present. root access is NOT correctly configured for this file! what is wrong and what do I need to do? I have been using the phone for a week downloading apps from blackmarket and googls app sometimes its kinda slow but It wont let me move systems apps to sd,can delet but not movei have titanium bu supersu busybox pro force2sd esfx and rommaneger how or can I gain full root for kitkat 4.4 lg fuel?
Click to expand...
Click to collapse
It's the new security features of kitkat. Only allows apps to access their own folders. Try SDFix (root app from play store ). I now can read, write, copy to/ from sd or system.
Sent from my LGL34C using XDA Free mobile app
---------- Post added at 09:16 PM ---------- Previous post was at 08:55 PM ----------
@FlyingPoo
Some things that I noticed that were missing (besides /sbin/recovery). There is no flash_image, dump_ image, or erase_ image in /system/ bin. Usually use flash_ image in terminal or in fastboot. Don't know if these binaries are generic, or device specific (partitions). Could copy from other device, but don't know if they will work properly. Glad I'm not alone in this.
Sent from my LGL34C using XDA Free mobile app
---------- Post added at 10:00 PM ---------- Previous post was at 09:16 PM ----------
[/COLOR
@FlyingPoo
What cwm are you going to use? Optimus Zone? Or did you compile it for the fuel?
Sent from my LGL34C using XDA Free mobile app
ibub said:
What cwm are you going to use? Optimus Zone? Or did you compile it for the fuel?
Click to expand...
Click to collapse
I pulled the one in the Zone since that phone is most similar to ours, However I have a feeling the key bindings won't be correct, so I may still have to compile from source. I pulled the git for TWRP but haven't made changes to it yet. Its been a busy week at work and its only monday.
---------- Post added at 08:49 PM ---------- Previous post was at 08:27 PM ----------
ibub said:
Some things that I noticed that were missing (besides /sbin/recovery). There is no flash_image, dump_ image, or erase_ image in /system/ bin. Usually use flash_ image in terminal or in fastboot. Don't know if these binaries are generic, or device specific (partitions). Could copy from other device, but don't know if they will work properly. Glad I'm not alone in this.
Click to expand...
Click to collapse
Those also don't exist in the stock recovery for the Optimus Zone. It looks as if busy box was added to the Zone CWM recovery now that I have looked at it closer. Its been a WHILE (Samsung Vibrant with Team Whiskey) since I built a recovery image.
FlyingPoo said:
I pulled the one in the Zone since that phone is most similar to ours, However I have a feeling the key bindings won't be correct, so I may still have to compile from source. I pulled the git for TWRP but haven't made changes to it yet. Its been a busy week at work and its only monday.
---------- Post added at 08:49 PM ---------- Previous post was at 08:27 PM ----------
Those also don't exist in the stock recovery for the Optimus Zone. It looks as if busy box was added to the Zone CWM recovery now that I have looked at it closer. Its been a WHILE (Samsung Vibrant with Team Whiskey) since I built a recovery image.
Click to expand...
Click to collapse
Yeah, we might only get one shot at success (before jtag ), so it's probably best to compile from our recovery and source. I used Apktool to decompile recovery (dd if =dev/ block/ mmcblk0p17 of =/cache/ testrecovery/recovery.img). Ramdisk has./ sbin/recovery. Copied that to /Sbin/ . Disappears after reboot. Haven't yet decompiled boot.img. Hoping to find "boot", and fastboot. More later.
Sent from my LGL34C using XDA Free mobile app
@FlyingPoo
Do you know anything about the Loki tool by Dan Rosenberg:
https://github.com/djrbliss/loki/blob/master/README.txt
Have to admit that I'm not quite this educated, but that looks promising.
Edit: This is like having to root your phone twice. Lol
EDIT: Don't nuke laf yet! I dd and decompiled it (had to rename it to boot.img in Apktool). There are some interesting images (png) in res folder. I'm gonna dd aboot and abootb, and see what's there. Gotta go to work soon. Probably more tomorrow.
Sent from my LGL34C using XDA Free mobile app
ibub said:
@FlyingPoo
Do you know anything about the Loki tool by Dan Rosenberg:
https://github.com/djrbliss/loki/blob/master/README.txt
Have to admit that I'm not quite this educated, but that looks promising.
Edit: This is like having to root your phone twice. Lol
EDIT: Don't nuke laf yet! I dd and decompiled it (had to rename it to boot.img in Apktool). There are some interesting images (png) in res folder. I'm gonna dd aboot and abootb, and see what's there. Gotta go to work soon. Probably more tomorrow.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for all your work. Im also very interested in being able to boot into stock recovery. Mainly to be able to preform a factory reset. Do you know of an alternative method to do a factory reset at this time since booting into any recovery isnt possible ATM?