I am in the process of updating and expanding this thread to a useful state, so it's a bit disorganized right now.
Don't panic.
The first step in recovering your device is to examine the situation. Which variant of the Galaxy Player 5.0 do you have? If you have a 3.6, 4.0, or 4.2, leave now before you break something! If you have a physical home button (that moves when you push it), you have an "international" device. If your home button is flat, you have a "USA" device. If you have a Korean or 16GB model, ask and I will add more specific instructions.
Next, what is your problem?
My device will not turn on, and is stuck at a black screen.
First, of course, make sure the battery is not dead. If the screen does not show anything even with the device plugged in, go to step 1.
My device only shows a black screen with "Phone -- ! -- PC" in the middle.
You are actually in download mode. It just looks different. Go to step 2.
My device shows a mostly black screen with a "loading" circle in the middle when I turn it on, but still can enter download mode.
Drain your battery fully, and you should be fixed. See *link* for more information.
My device shows a yellow triangle with "Downloading" at the top.
You are in download mode. If you are stuck here, you need to flash a kernel. Go to step 2.
My device is stuck at a non-animated Samsung logo.
You need to flash a kernel or a firmware. Head to step 2.
My device is stuck at a boot animation indefinitely.
You are in what is called a "boot loop." See step 4.
My device boots fine. I just want to make a backup.
Good job thinking ahead. See post four for instructions.
I not know what download mode is.
Step 2 gives a brief explanation.
I do not know what CWM is.
Step 3 gives a brief explanation.
I cannot flash things in download mode, even with a PIT.
See the section of post three about DD dumps and fdisk.
I just want to go back to stock
See step 2.
Step 1 - Restoring Bootloaders
If your device is stuck at a completely black screen (no Samsung logo), then something is wrong with the Player's boot loaders. Your device cannot do anything until these are fixed (as they provide the download mode used in step 2). There is a tool that can help you fix them, but it does not work in every case. If it does not work for you, there is nothing you can do but pay someone to fix your player, or send it back to where you bought it from.
What you will need:
A computer running Linux (if you have never used Linux before, Ubuntu is considered a good place to start).
A USB cable and a port on the back of your computer (if it is a desktop). No hubs!
Boot into Linux and make sure Java is installed. Download *tool*, *bootloaders*, *heimdall* and the *appropriate PIT for your device*.
To run the Unbrickable Resueerctor tool, double-click the .jar file (or right-click and open with java), or on the command line, run
Code:
java -jar ~/path/to/jarfile
Technical Explanation:
Step 2 - Flashing a Kernel
Now that your device has functional boot loaders, you can enter and use download mode. There are two tools you can use on your PC to flash things while your device is in this mode: Odin and heimdall. Odin is proprietary software made by Samsung that only runs on windows; heimdall is an open-source, cross-platform replacement.
Technical Explanation:
Step 3 - Flashing Firmware
Technical Explanation:
Step 4 - Getting out of a boot loop
The simple solution is to boot into recovery and "wipe data/factory reset." The next boot will take a while, but it should succeed. If it does not, you will need to re-flash your firmware.
Technical Explanation:
There are 3 reasons you can get into a bootloop:
Missing/corrupted system files
Data left over from a previous firmware
Unsupported or corrupted filesystem
Fixing partitions the hard way
The fdisk method
This requires more typing and is more prone to error, but may take less time and is the only way if your device variant does not have an available dd dump.
Technical Explanation:
The dd method
Some people have gotten themselves into a place where their partitions are messed up and repartitioning with a PIT file is of no use. As an alternative to the fdisk method, here is a full dd dump for use in recovering your player. This file WILL NOT get you fully up and running again by itself. DO NOT flash it with Odin. In order to make the file small enough to not take days to download (literally), I zeroed out some partitions that would have gotten formatted anyways. Please read the instructions for use below. If you want to make a dump of your player, see instructions in the second post.
Files
Mevordel's SGP 5.0 (post-JTAG): http://www.mediafire.com/?ugzfkcaqcq1cacs (There is a small possibility that this file may have some issues - remember, I had to get my player JTAG'd - but I wouldn't worry too much, as it boots my player now. If you're paranoid, ask in the thread for someone else to make one.)
Get your player into CWM recovery mode. I don't care how. Recommended way: use resurrector if needed to flash Entropy512's kernel in download mode.
Download a dump file onto your computer.
Write file to your device. There are three basic options here.:
Use an SD card. Once you've downloaded the file, extract it, and, on your Linux-based system (like Ubuntu), find out the device node associated with your SD card by running 'dmesg' in a terminal right after plugging it in. It should be a three-letter code in brackets starting with 'sd', like '[sdc]'. When you type it later, do not type the brackets. Make sure it is unmounted, and then, in the terminal, run:
Code:
dd if="/path/to/extracted/mmcblk0" of=/dev/sdX && sync && sync
where sdX is the node you found earlier. This will erase everything on your SD card! Now put your SD card in your player. Open up an ADB shell and type:
Code:
dd if=/dev/block/mmcblk1 of=/dev/block/mmcblk0 bs=32768 count=242432
This will take a few hours, so make sure your computer does not go to sleep, and do not unplug your player, or you'll have to start over. Once it is done, run 'sync' a few times, and exit the ADB shell. Now move to step 4. (To put your SD card back to normal, put it back in your PC and use gparted or WIndows Disk Manager to delete all of its partitions and create a new FAT32 partition filling it up.)
ADB push. This is untested, but it should work. (If adb complains about running out of space, you'll have to try another way, and please report back.) Extract the lzma file on your computer. Then open a terminal/command prompt and run:
Code:
adb push /path/to/extracted/mmcblk0 /dev/block/mmcblk0
This will take an hour or two, so make sure your computer does not go to sleep, and do not unplug your player, or you'll have to start over. Once it is done, run 'adb shell sync' a few times for good measure, and move on to step 4.
Extract the file on your device. This is the least likely to work, but may be the fastest. Open a terminal/command prompt and run:
Code:
adb push /path/to/downloaded/mmcblk0.lzma /tmp/
Now in an ADB shell, run:
Code:
lzcat /tmp/mmcblk0.lzma > /dev/block/mmcblk0
This will take a few hours, so make sure your computer does not go to sleep, and do not unplug your player, or you'll have to start over. If you get errors about running out of memory, I can try using a different compression format, but you're basically out of luck. Once it is done, run 'sync' a few times, and exit the ADB shell. Now move to step 4.
Optionally, unplug your player, use the CWM menu to turn it off, and enter recovery with the button combo. This will test if the write was successful. If you try the button combo a few times and can't get it, try flashing again or use a different method.
In CWM, go to 'Mounts and Storage,' and format /system, /datadata, /cache, and /data. (For some reason, formatting /emmc does not work, but that's not really an issue.)
Install a (preferrable stock or stock-based) firmware. Either reboot into download mode and use Odin (without repartitioning!) or install a zip from the external SD card.
Reboot into Android. It will tell you you need to format your storage. Do it. If it fails, go to Settings -> SD card and device storage -> Format USB storage.
???
Profit!
Technical Explanation:
Making/Restoring a Backup
/efs Backups
Technical Explanation:
"Nandroid" Backups
Technical Explanation:
Odin/Heimdall-Flashable Backups
Making an Odin or Heimdall-flashable backup involves pulling partitions off your device onto your computer, and then packaging them in a way Odin or Heimdall will understand. First, here is a table of all of the partitions on your device. It shows their device names, their sizes, and the PIT-mapping file name (the name Odin uses).
Code:
Device Size (KiB) Mount Name Notes
/dev/block/mmcblk0 7757824 Internal eMMC disk device
/dev/block/mmcblk0p1 1 Extended partition containing everything else
/dev/block/mmcblk0p5 256 boot.bin Initial+Primary Bootloaders
/dev/block/mmcblk0p6 256 YPG70_8G-0304.pit Partition Information Table
/dev/block/mmcblk0p7 1280 Sbl.bin Secondary Bootloader
/dev/block/mmcblk0p8 1280 Sbl.bin SBL backup
/dev/block/mmcblk0p9 5120 /mnt/.lfs param.lfs param.blk and boot logos - source of recovery loops
/dev/block/mmcblk0p10 10240 /efs efs.rfs WiFi and BT MAC addresses - causes missing lockscreen
/dev/block/mmcblk0p11 7680 zImage Kernel
/dev/block/mmcblk0p12 7680 zImage "Recovery" kernel that is never used
/dev/block/mmcblk0p13 296960 /system factoryfs.rfs System partition
/dev/block/mmcblk0p14 137216 /dbdata dbdata.rfs Various Android/app databases
/dev/block/mmcblk0p15 65536 /cache cache.rfs Cache partition
/dev/block/mmcblk0p16 1970176 /data datafs.rfs Data partition (apps and their data)
/dev/block/mmcblk0p17 5252096 /sdcard userfs_8G.rfs "Emmc" "Usb Storage" - where your media goes
/dev/block/mmcblk1 <varies> External SD Card disk device
/dev/block/mmcblk1p1 <varies> /sdcard/external_sd External SD Card partition
Pulling files off your device
Many of these files are in use while android is booted (they are mounted filesystems), so it is highly recommended to extract the files in recovery. To do that, you will need an "insecure" kernel--one that gives you root access in CWM, like Entropy's or rj's. Either way, you will need adb. Enter a root shell, and for each partition you want to back up, run the following, with device and name coming from the appropriate columns in the table above.
Code:
adb pull <device> <name>
Putting them in an Odin tar
Making a Heimdall One-click package
Technical Explanation:
This partition information was taken from the commands "mount" and "cat /proc/partitions" on the device, and "heimdall print-pit" on the PC.
Thanks again for this image. I just got my player working again and am in the process of restoring it right now. I can say so far that methods 'b' and 'c' didn't work for me. B complained about no free space after 30 mins or so, and C gave some protocol error with an unknown status.
I'm about to give the first option a try and see how that goes. I don't have an SD card reader though so I'm gonna try restoring the Image through my phone.. don't see why it wouldn't work but I guess well see.
Ok, so I got the image copied from my phone internal memory to the sd card with terminal emulator. Popped the SD card in my SGP, ran the dd command through adb shell and after copying for an hour or so now my player is completely unresponsive again. I can use UnBrickable to get back into download mode, but nothing I flash will stick and I keep getting a "there is no PIT partiton" error in ODIN, even after flashing a PIT. I also can't get into CWM anymore so I can't try copying mmcblk0 again with ADB.
Any ideas? Is there a way to flash the entire mmcblk0 with ODIN? Or maybe you could split the partitions up?
I'm a N00B and I had my SGP YP-G70 intl accidentally bricked. I've been doing my best to learn with my mistake and to learn geeking to recover the SGP.
It's been very dificult to me but I won't give up. I was able to use the Unbrickable Resurrector R40 to get SGP into download mode. I flashed the Froyo ROM, Bootloaders provided in Adam's thread and r14 kernel. All of them says PASS in Odin, despite that SGP wont reboot or turn on.
I really need your help to find out what is going wrong. I suspect something is wrong with Bootloaders or something.
Would that be possible to drive me step by step to make it using Heimdall and share the appropriate YP-G70 Intl files I will need?
Thanks in advance.
mrlightman said:
I'm a N00B and I had my SGP YP-G70 intl accidentally bricked. I've been doing my best to learn with my mistake and to learn geeking to recover the SGP.
It's been very dificult to me but I won't give up. I was able to use the Unbrickable Resurrector R40 to get SGP into download mode. I flashed the Froyo ROM, Bootloaders provided in Adam's thread and r14 kernel. All of them says PASS in Odin, despite that SGP wont reboot or turn on.
I really need your help to find out what is going wrong. I suspect something is wrong with Bootloaders or something.
Would that be possible to drive me step by step to make it using Heimdall and share the appropriate YP-G70 Intl files I will need?
Thanks in advance.
Click to expand...
Click to collapse
My suggestion is you should post opening a new thread related to your issue because your request will stay buried in this OP and may be never answered as well.
In order to understand what's going on tell if your are able to go to recovery and wipe everything. If done what are the messages given at this step. this would clarify in case of "poluted partition".
Thanks
---------- Post added at 10:00 AM ---------- Previous post was at 09:57 AM ----------
Many Thanks Mr Mevordel, this is a great achievment.
mrlightman said:
I'm a N00B and I had my SGP YP-G70 intl accidentally bricked. I've been doing my best to learn with my mistake and to learn geeking to recover the SGP.
It's been very dificult to me but I won't give up. I was able to use the Unbrickable Resurrector R40 to get SGP into download mode. I flashed the Froyo ROM, Bootloaders provided in Adam's thread and r14 kernel. All of them says PASS in Odin, despite that SGP wont reboot or turn on.
I really need your help to find out what is going wrong. I suspect something is wrong with Bootloaders or something.
Would that be possible to drive me step by step to make it using Heimdall and share the appropriate YP-G70 Intl files I will need?
Thanks in advance.
Click to expand...
Click to collapse
Your best bet is to flash boot loaders only with the correct PIT. Then try going into download mode.
Sent from my Galaxy Nexus
lolo9393 said:
My suggestion is you should post opening a new thread related to your issue because your request will stay buried in this OP and may be never answered as well.
In order to understand what's going on tell if your are able to go to recovery and wipe everything. If done what are the messages given at this step. this would clarify in case of "poluted partition".
Thanks
---------- Post added at 10:00 AM ---------- Previous post was at 09:57 AM ----------
Many Thanks Mr Mevordel, this is a great achievment.
Click to expand...
Click to collapse
Thanks for the suggestion, I've already tried to open a new thread but had no answers.
I cant get it into recovery mode, is there any way to force it. What I can do is get it into Download Mode, using Unbrickable Ressurector, so I flash it using Odin but it wont boot or turn on.
Really need help from experienced people: senior members.
Thank you very much
---------- Post added at 04:35 AM ---------- Previous post was at 04:32 AM ----------
Mevordel said:
Your best bet is to flash boot loaders only with the correct PIT. Then try going into download mode.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I've tryied that too, the matter is that I can't enter into download mode without using Unbrickable Ressurector 'cause when I flash the bootloaders or ROMs the process goes till the end and says: SUCESS but SGP wont turn on or reboot by itself.
Please give me some light.
Regards
mrlightman said:
Thanks for the suggestion, I've already tried to open a new thread but had no answers.
I cant get it into recovery mode, is there any way to force it. What I can do is get it into Download Mode, using Unbrickable Ressurector, so I flash it using Odin but it wont boot or turn on.
Really need help from experienced people: senior members.
Thank you very much
---------- Post added at 04:35 AM ---------- Previous post was at 04:32 AM ----------
I've tryied that too, the matter is that I can't enter into download mode without using Unbrickable Ressurector 'cause when I flash the bootloaders or ROMs the process goes till the end and says: SUCESS but SGP wont turn on or reboot by itself.
Please give me some light.
Regards
Click to expand...
Click to collapse
Try using heimdall.
Sent from my Galaxy Nexus
Uh
The Show Content of step 2 flashing a Kernel does not work.
Kenobz said:
The Show Content of step 2 flashing a Kernel does not work.
Click to expand...
Click to collapse
I know. I have not been able to finish writing this guide (see the note at the top).
Mevordel said:
I know. I have not been able to finish writing this guide (see the note at the top).
Click to expand...
Click to collapse
Could you please respond to my thread above yours it has something to do with a step missing.
Stuck on blank_efs.img message in Odin
I have the us version, and I'm flashing the restore package butt in Odin it has been stuck at this message for like 20 min
"<ID:0/006> blank_efs.img"
My player is still connected and still in download made though, and it seems Odin is still running but idk...I'm worried.
I'm usually good at these i never bricked anything beyond fixing.
i don't know if I'm being impatient or i effed up my thing. should i wait longer or take action?
Daze7 said:
I have the us version, and I'm flashing the restore package butt in Odin it has been stuck at this message for like 20 min
"<ID:0/006> blank_efs.img"
My player is still connected and still in download made though, and it seems Odin is still running but idk...I'm worried.
I'm usually good at these i never bricked anything beyond fixing.
i don't know if I'm being impatient or i effed up my thing. should i wait longer or take action?
Click to expand...
Click to collapse
That is because there is no partition to match that filename. Where did you get this package? You probably don't want to wipe your /efs (it's unique to your device), so you probably want to remove it from the package.
Sent from my Galaxy Nexus
Mevordel said:
That is because there is no partition to match that filename. Where did you get this package? You probably don't want to wipe your /efs (it's unique to your device), so you probably want to remove it from the package.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Whoops, I am so sorry, i accidentally posted in this thread. I guess i had to many tabs open . My problem pertains to the [STOCK ROM] Full Recovery For Samsung Galaxy Player/S Wifi 4.0 thread not the 5.0. So the advice you gave me won't help i dont think...I'm sorry how do i delete these?
Daze7 said:
Whoops, I am so sorry, i accidentally posted in this thread. I guess i had to many tabs open . My problem pertains to the [STOCK ROM] Full Recovery For Samsung Galaxy Player/S Wifi 4.0 thread not the 5.0. So the advice you gave me won't help i dont think...I'm sorry how do i delete these?
Click to expand...
Click to collapse
You should probably ask for help on that thread then.
My Player 5 INTL doesn't pass from Recovery or Download
Hi guys, I need a bit of help with mi device. I own a Galaxy Player 5 INTL, which I had working with CM 10.2. I needed to install again the stock rom, so I looked for it and flashed with odin. I don't know what exactly happened, but it got hardbricked. I followed a few tutorials in xda, and after using Unbrickable Resurrector, I could flash a Russian Froyo ROM (it apparently has the bootloader and a pit within it), so know it boots. But It never goes beyond the recovery mode. It always says that it can't find or mount /efs, /cache, /recovery, etc. There are some other CSC stuff. I've flashed a stock rom, an Erygit one, an DowloadModeOnly bootloader from the hardbrick tutorial (which never goes out from that mode). Now I'm going to test the dd way to rebuild partitions. Any other idea? Please, I would really apreciate any help.
EDIT: I just realized that I don't have any SD card bigger than 4gb. I can't use push from adb, because it simply doesn't allow me to copy such an huge file.
nhermosilla14 said:
Hi guys, I need a bit of help with mi device. I own a Galaxy Player 5 INTL, which I had working with CM 10.2. I needed to install again the stock rom, so I looked for it and flashed with odin. I don't know what exactly happened, but it got hardbricked. I followed a few tutorials in xda, and after using Unbrickable Resurrector, I could flash a Russian Froyo ROM (it apparently has the bootloader and a pit within it), so know it boots. But It never goes beyond the recovery mode. It always says that it can't find or mount /efs, /cache, /recovery, etc. There are some other CSC stuff. I've flashed a stock rom, an Erygit one, an DowloadModeOnly bootloader from the hardbrick tutorial (which never goes out from that mode). Now I'm going to test the dd way to rebuild partitions. Any other idea? Please, I would really apreciate any help.
EDIT: I just realized that I don't have any SD card bigger than 4gb. I can't use push from adb, because it simply doesn't allow me to copy such an huge file.
Click to expand...
Click to collapse
If you getting something like this read this entire thread.
It is what a see in my device, but...
Meticulus said:
If you getting something like this read this entire thread.
Click to expand...
Click to collapse
Thanks for replying, Meticulus, I read it entirely, and was about to do the fdisk verification, but it didn't work the same as in the other case. I attached a capture with the results of each command.
Related
So basically i got the ICS Encryption unsuccessful error and now my phone wont get past the vibrant splash screen. I tried odining back to stock but it just goes to splash screen and then turns off. i cant get into recovery mode. please please pleaseeee help!
jig or get to download mode
odin EUGENE373_SamsungS_Froyo_PDA (read directions)
then flash back to stock then try not too "brick" the unbrickable vibrant again.
this does not fix the problem. the /data partition is the cause of the problem and i dont know how to fix it. repartitioning in odin doesn't fix it either. :/
I had the same thing happen to me.. ive tried everything i could think of
enter download mode
dvryu said:
enter download mode
Click to expand...
Click to collapse
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Unfortunetly there is no fix as of now. The problem seems to be the internal flash memory 16gb is unable to mount. SD card (External) mounts perfectly fine as i was able to pull some files using adb commands. Hope you have a spare phone cuz there is no way to fix your phone as of today.
A warning to ICS rom users. You phone could potentially become paperweight so be extremely careful. You might want to consider using Gingerbread or some other rom other than ICS until someone finds a solution to this problem.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Nirmalspeed said:
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Click to expand...
Click to collapse
The buttons in recovery don't work after flashing Eugene's rom.
You can only reboot your phone through the adb command:
adb reboot
Of course you must also have the android debugging bridge installed on your computer to issue these commands. Including the SDK. Good luck.
i have two other vibrants in my family right now. what do you think i could do with those to fix mine?
http://forum.xda-developers.com/showthread.php?t=1447303
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Woodrube said:
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Click to expand...
Click to collapse
i was running ICS Passion 13 with the Kiss kernel that came with it. and i've looked around and many people with ics have gotten this problem both on our device and on the AT&T's captivate.
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
cotbu said:
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
Click to expand...
Click to collapse
that wouldn't work as the /data partition isn't being red by the phone. Nothing happens when i try that command.
These are the instructions, Eugene's rom write like a lowlevel format, either you are not following directions or you actually bricked the vibrant.
But....you say you've made it to Eugene's recovery if you did you should be good to go.
Okay, Now with the Caution Posted, Lets Begin with the Froyo that Don't Brick
I have Tested this 5 Time's to Make Sure! Only install What I Post!
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Do Not Select Repartition In ODIN Flasher
Quote:
Installing...
Extract the .zip file
Open ODIN Flasher, Select the Pit File.
Select Eugene373_GalaxyS_Froyo_PDA.tar
Select start..
Second,
Once Odin had Done Flashed, & you are in Recovery Mode you will not be able to Access anything & need to be at a Computer with Samsung Driver's installed & a working SDK pre-installed..
Side note: you will get an error in recovery, Don't be worried!!!! Ignore this!
Third,
Open a CMD Prompt & type:
Quote:
adb reboot
Froyo with Downgrading back to Stock Possible:
Download here > EUGENE373_SamsungS_Froyo_PDA.zip
*Stock Froyo with*
~ Root
~ SuperUser.apk
~ Build.prop now Correct
~ Defualt.prop Also Correct
****
*Issue's
Volume Key are Reversed
****
*Not working*
~ Rom Manager via reboot to Recovery!
~ Selectable Menu in Recovery
~ 3.5 Head-jack
~ Hot Spot Tethering
sorry for stressing but, I have a 4yr old that loves playing with the vibrant and I think I've brought it back from every brick situation possible. As long as the vibrant has power, it will not stop! xd!
SOLVED, see post #6
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
=JKT= said:
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
Click to expand...
Click to collapse
okay, I just found out that I can access adb in the state that recovery is in.
Is it possible to reflash either the rom or the recovery from a shell in here? or would that be "bootstrapping" since I'm already in recovery?
perhaps I can adb push a backup to /system?
of course the ./adb reboot bootloader doesn't work
I'm using a mac and I've had trouble getting fastboot to recognize my device in the past...I think last time I just borrowed someone's pc to do it.
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Can't test it right now, but I think the process would go something like this (recovery means on the phone, computer means on the computer):
Code:
[I]recovery>[/I] mount /sdcard
[I]computer>[/I] adb push recovery.img /sdcard/
[I]recovery>[/I] flash_image recovery /sdcard/recovery.img
[I]recovery>[/I] umount /sdcard
[I]recovery>[/I] reboot recovery
Note once again that this is untested, it's straight from my head, so it might need adjustments.
ravilov said:
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Click to expand...
Click to collapse
thanks for the idea. I can't access any of the functions of the recovery. it's just a splash screen. ADB recognizes the device on my computer though. I can adb push files...I'm wondering if I can push something from a backup to my phone through adb. I guess I'd need to push the /system and /boot to it. I can't seem to get mmcblk0p12 to mount though...
edit: I didn't see the code you added.
I tried it and got this message:
error scanning partitionsfailed with error: -1
I can't seem to get any partitions to mount (ie mmcblk0p12 etc)
I'm nervous about totally borking recovery since it's my only access to the phone right now. I might have to borrow a pc to get fastboot to work.
=JKT= said:
I might have to borrow a pc to get fastboot to work.
Click to expand...
Click to collapse
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
[SOLVED]
ravilov said:
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
Click to expand...
Click to collapse
SOLVED!!
First I found out that if I type fastboot -i 0x22b8 before every command, they worked fine.
then I stumbled across moto-fastboot, which is apparently a special fastboot for moto devices.
I used that to flash a new recovery the standard way and it worked out just fine.
Thanks so much for your help, ravilov!!
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
ravilov said:
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
Click to expand...
Click to collapse
I've only had the Atrix for about a week. Still learning the ropes: coming from an HTC device, so I'm used to doing things a certain way and relearning some basics lol
Cheers!
Sent from my MB860 using xda app-developers app
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
bmxer4130 said:
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
Click to expand...
Click to collapse
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
lolo9393 said:
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
Click to expand...
Click to collapse
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
bmxer4130 said:
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
Click to expand...
Click to collapse
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
lolo9393 said:
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
Click to expand...
Click to collapse
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
E: Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So yeah, its the internal memory.. now if i could just get adb shell to work right
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
bmxer4130 said:
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
Click to expand...
Click to collapse
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
lolo9393 said:
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
Click to expand...
Click to collapse
Ok, I was able to adb shell and rebuild the partition table, and it was indeed messed up, and I can mount usb storage, but I still can't get it to boot into any rom, and it refuses to boot into cwm recovery unless its just rebooted from odin. in recovery in the log it has an error about libc.so, idk if that has anything to do with it though. I'm beginning to think the problem may have to do with my usb cable. I accidentally switched the stock one with a Galaxy SII one, which should be fine, but maybe not.
bmxer4130 said:
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
So yeah, its the internal memory.. now if i could just get adb shell to work right
Click to expand...
Click to collapse
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Mevordel said:
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Click to expand...
Click to collapse
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
bmxer4130 said:
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
Click to expand...
Click to collapse
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
lolo9393 said:
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
Click to expand...
Click to collapse
Yes, I tried flashing it in cwm, along with eryigit (both with entropys kernel flashed over them) and PA venturi, but it refuses to boot properly. If it is the bootchain, how can I get a dump of a working one?
And I was able to dump a lot of stuff from [adb pull */*] and can access logs and dmesg, but havent inspected them fully. Is there an easy way to read the boot log and/or setup a custom log to run preboot? I figure that wouldnt be necessary since the linux kernel does a fine job of logging itself.
And yes I think I am skilled enough now, just was confused how to get to the adb shell, but I'm fairly well versed in linux, so the shell is relatively comfortable for me.
But if I'm able to figure it out I'm going to make a How To thread including what I've found and what you've found and posted to make it easier for nooblets in the future, maybe even make a simple shell script to repartition the US 8gb model.
I fixed it
how?
Jistropy said:
how?
Click to expand...
Click to collapse
Mainly luck hehe. But actually from the mentioned threads ^^^^^ and this nifty trick, but use caution as I have no clue how well this works for other devices, if it all. And a large part of the problem was that my battery was dead because it wasn't charging correctly when plugged into my computer; and it kept dying in Odin.
Do you have a similar problem?? I can probably help..
If anyone here could offer any tips or advice, I would appreciate it.
I opened my gTab up to resolder the charge port and all went well. I am a very meticulous person. I even take pictures, go slow and do not make dumb mistakes. But... somewhere I did make a mistake, I guess.
Charge port connector works fine now. Wiggle the charge cable and no interruption or blinking on the indicator light.
But... after putting the motherboard back in and testing it, It sticks at the birds. Thought SOMEHOW I must have bricked it because the charge port repair went perfectly. All connectors snugly in their place and oriented correctly.
I have VeganTab 7.0 Ginger and an older CWM on it (non touch). (or rather I did) So I tried to redo a new rom, booting into CWM. I get the standard "recovery key detected" and "booting recovery kernel image" messages at top left.
But, it just sticks there.
So I decided to try the NVFlasher method here: http://raywaldo.com/2011/01/nvflash-for-dummies/
I tried both the 250 and 300 meg partition file.
Wow... went right into APX mode. (I did not expect it to) I ran the nvflasher file and it seemed to finish correctly and successfully.
When I tried to boot into the newer CWM that's in the package, I still see the older CWM come up and it sticks there as it did before.
I tried rewriting files a couple more times but got the same results.
Part of the prob is I guess, is that I don't remember what bootloader was on ot. 1.1 or 1.2.
Also... does the fact that the nvflasher could write to the internal sd card mean that it is ok and I did not screw something up when I did the charge port repair? Well... I mean, I can not verify that it wrote correctly but it seemed to and said "completed successfully".
I was supposed to be selling this to a lady at the Moose lodge today. She has already paid me money on it
Can anyone help me out here or is all lost?
Thank you for your time,
John Dumas
pede69 said:
I opened my gTab up to resolder the charge port and all went well. I am a very meticulous person. I even take pictures, go slow and do not make dumb mistakes. But... somewhere I did make a mistake, I guess.
Click to expand...
Click to collapse
Did you take the appropriate anti-ESD (electrostatic discharge--static electricity) precautions whilst working on the board? Other people here have--from their problem descriptions which match yours--I think, fried some component on their board while fixing the same charge port problem.
Part of the prob is I guess, is that I don't remember what bootloader was on ot. 1.1 or 1.2.
Click to expand...
Click to collapse
If you do a full nvflash (and the images were written correctly), then bootloader version doesn't matter since the bootloader and the kernels in the images will match.
Also... does the fact that the nvflasher could write to the internal sd card mean that it is ok and I did not screw something up when I did the charge port repair? Well... I mean, I can not verify that it wrote correctly but it seemed to and said "completed successfully".
Click to expand...
Click to collapse
Nvflash does not write to the internal SD card--only CWM or the ROM can manipulate it. Nvflash only works on the built-in NAND flash chip. Ie. There are 2 separate storage devices on the gTab.
Ordinarily, based on the on-screen error messages, I would've said that it was a bootloader/kernel mismatch problem, but, this quote of yours below makes me think that it might be a NAND flash problem:
When I tried to boot into the newer CWM that's in the package, I still see the older CWM come up and it sticks there as it did before.
I tried rewriting files a couple more times but got the same results.
Click to expand...
Click to collapse
Both Recovery and the ROM kernel are read from the NAND flash and then is booted into. So, if you can't get into CWM, then you'll have to:
1. Check if the NAND flash is OK by writing to the device partitions and then reading the important partitions back and comparing the resulting image files byte-for-byte. See this post for the read command to be used after doing a full nvflash.
2. If the NAND flash checks out OK, then use a custom kernel which prints diagnostics to see if it detects any other HW problems. See this post for that. The modified kernel is for bootloader version 1.1 only, so you'll have to be on that bootloader to run it.
Awesome reply... Thank you.
I have formated using nvflash and went to write the file but the zip file that I downloaded did not have a bat file in it to tell nvflash what to do. The files came from here:
http://forum.xda-developers.com/showthread.php?t=861950 >>> "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Neither has a bat file to start an nvflash write.
And no, I did not use an anti-static bag. I know it can happen but I have been repairing computers for 20 years and have not zapped anything yet
I'm getting confused now. Can you point me to the correct file to load with nvflash?
Oh yeah... how do I figure out which bootloader I'm on?
You are most awesome for helping, thank you very much.
John
pede69 said:
I have formated using nvflash and went to write the file but the zip file that I downloaded did not have a bat file in it to tell nvflash what to do. The files came from here:
http://forum.xda-developers.com/showthread.php?t=861950 >>> "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip"
Neither has a bat file to start an nvflash write.
Click to expand...
Click to collapse
According to that thread, it does. The file is called "nvflash_gtablet.bat". You might try to: open a CMD.exe window, change to the correct directory and then type: .\nvflash_gtablet
And no, I did not use an anti-static bag. I know it can happen but I have been repairing computers for 20 years and have not zapped anything yet
Click to expand...
Click to collapse
"Yet"--Always a first time, no?
Oh yeah... how do I figure out which bootloader I'm on?
Click to expand...
Click to collapse
As I said, if you do a full nvflash (ie. create, format, and write all the partitions on the NAND flash), then bootloader version does not matter, as the nvflash zip package will have the bootloader and the correct boot and recovery kernels in the image files to match that bootloader. Still, if you want to determine your bootloader version, see this thread.
What you should do first is write bekit's nvflash package to the NAND, then read the important partitions back, then do a byte-compare. I don't use, or have, Windows, but, I recall a MS-DOS command called fc which might still be present on the newer Windows variants:
Code:
C:\SOME\PATH> [B]fc /b [I]file1.img[/I] [I]file2.img[/I][/B]
Do a file compare using fc on the original image file and the read-back image file. If fc reports that one of the files is smaller/larger but reports no differences, then that's OK because a NAND partition read using nvflash reads the whole partition and not just the image that needs to be written to that partition.
If fc reports that the files are the same, then you can move on to step 2 of post #2.
Thanks again for the info. I will try to absorb and apply what you suggest.
BTW... I only asked the bootloader question because of what you mentioned above... "custom kernel which prints diagnostics - only works with 1.1"
Thank you for being there for me. I'll see what I can do now.
John
PS - Here are the unzipped files from nvflash_gtablet_2010110500.zip
pede69 said:
BTW... I only asked the bootloader question because of what you mentioned above... "custom kernel which prints diagnostics - only works with 1.1"
Click to expand...
Click to collapse
If you write bekit's image files, then you'll be on a 1.1 bootloader.
PS - Here are the unzipped files from nvflash_gtablet_2010110500.zip
Click to expand...
Click to collapse
As the thread says, you need to download two zip files. The batch file is in the other one: nvflash_windows_20100500.zip.
OK... I ignored the windows one because there are no instructions to use it and I thought it was for setting up APX on Windows. So I will re-read the instructions again and see what I may have overlooked, and If I can figure out how to use the both of them.
Thank you,
John
OK... after I get my foot out of my mouth, I'll give it a whirl.
J
Well... put contents of both zip files in one folder and ran nvflash.
Said "Completed successfully"
Still boots to old CWM.
Will go read your other instructions now...
J
Well...
Linux is failing to complete.
The following link has some pics from the gTab screen and also three .img files that was created when running the command on the linked page you referred me to. I could not find a txt file that it created.
.\nvflash --bl bootloader.bin --read 4 ebt.img --read 9 rec.img --read 10 lnx.img
http://jaxehost.com/gtab/
So... I guess all is lost. Not sure how to proceed now.
Thanks,
John
pede69 said:
Said "Completed successfully"
Still boots to old CWM.
Click to expand...
Click to collapse
I'm slighty puzzled now--can you elaborate on this: How did you determine that your CWM is unchanged when you're always stuck at the 3 birds screen? Ie. When the gTab isn't booting into CWM where its version can be seen.
I had assumed thus far that you were going by the "Recovery key detected" & "Booting recovery kernel image" messages. Those are bootloader messages (not CWM!) and depending on the bootloader installed you can sometimes differentiate between different bootloaders by looking at what message is printed. But, this is not a definitive method as many bootloaders print the same messages.
pede69 said:
Linux is failing to complete.
The following link has some pics from the gTab screen...
...
So... I guess all is lost. Not sure how to proceed now.
Click to expand...
Click to collapse
The kernel is stopping at the same place as it is here. Except that it is taking ~20 seconds more than is usual to do so. I have to say that this is a HW problem--probably something on the board. The NAND might still be OK, though.
Inspect the place where you soldered, and around it, for stray solder traces or bridges. Otherwise, something on the board has gotten borked. Sorry.
Hey
Guess I'm giving up and giving the person their money back. Damn, I needed it...
What I was saying is that when I installed the old CWM, I used to access it my pressing the power + volume up button. I thought what I see now is what I seen before when it started it but I may be wrong.
Guess I'll koad bekit back on it.
So is there a file to load JUST the CWM script using nvflash?
Also... is there a diag program that I use nvflash to load that will do a NAND and SD Card test?
Thanks for everything,
John
pede69 said:
Guess I'm giving up and giving the person their money back. Damn, I needed it...
Click to expand...
Click to collapse
Technically, the tablet might not yet be a total loss. The error messages indicate that the soft-key controller (SO340010) is failing to respond. Assuming that this is the only HW problem (a big assumption--there might be other things wrong on the board), the kernels (both in the ROM and in CWM) could then be recompiled without that soft-key device driver. Neither CWM nor the newer ICS+ ROMs require those soft-keys anyway. If the new kernels boot, then the soft-key controller is the only problem. Otherwise, the error messages will again have to be looked at to see what else has failed.
As you can see, all this will involve a fair amount of diagnosing and work. You may be able to use the tablet because you know what's wrong and because you have a custom kernel for the ROM and CWM of your choice, however, I don't think the buyer would like to be stuck with only one choice of ROM. Also, if other critical controllers (the touchscreen or WiFi, for instance) have gone belly up, then there's little hope for any Android ROM.
What I was saying is that when I installed the old CWM, I used to access it my pressing the power + volume up button.
Click to expand...
Click to collapse
Recovery mode is always accessed using power and Vol +. These keys assignments, as far as I know, can't be changed.
Not entirely clear on what you're trying to say here...
So is there a file to load JUST the CWM script using nvflash?
Click to expand...
Click to collapse
This post.
Also... is there a diag program that I use nvflash to load that will do a NAND and SD Card test?
Click to expand...
Click to collapse
Because both the bootloader and both CWM and ROM kernels are loading and running, the NAND is very likely OK. If you want to check the NAND partitions, the standard method is to do a full nvflash, read back the partitions, then check the original and read-back images using fc as I've shown. Alternatively, you could try this technique (I haven't tried it, so tell me how well, or if, it works out):
Edit the batch file you're using to do the full nvflash, and add a --verifypart -1 to the nvflash command line, before the --create flag. Save and run the batch file as usual.
The SD card cannot be tested using nvflash. You need either CWM or a ROM for that.
Thanks rajeevvp...
I'll get back at this unit in a while. Between this and the S3 and Note II issues i'm going through, I need a break.
You any good with Verizon phones? hehe...
Thanks,
John
Thanks rajeevvp...
I'll get back at this unit in a while. Between this and the S3 and Note II issues i'm going through, I need a break.
You any good with Verizon phones? hehe...
Thanks,
John
pede69 said:
You any good with Verizon phones? hehe...
Click to expand...
Click to collapse
Sorry, no--can't help with hardware that I don't have.
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!