Okay, have had my Gtab since late November, initially rooted it and installed Google services (market and gmail), later flashed to TnT-lite 2.2 then 3.1.4. Flashed over to Vegan b5.1 recently everything was great......
Then I mistakenly "updated" ClockworkMod Recovery and it's been a crash and burn ever since.
Got the Magic Mis-Match or whatever and tried to correct that has now made my Gtab a non-functional paperweight.
I can NVFlash the stock image (or even the NVFlash of TnT-lite 1.02) and the tablet will boot after the flash and function. Power it off (or do something that requires a reboot) and the tablet will no longer function. No power on (that I can tell), can't boot to recovery......and if I plug the tablet in to the PC I can NVFlash it and it boots. It's like it's stuck in APX mode now. I just have to plug it in to the PC, no Power + Volume- combo.....just plug the USB in and run NVFlash. It boots (to whatever I flashed) and will run until I power it off or try to reboot.
I've pulled it open and pressed the reset button, I've drained the battery until the OS shut the tablet down and then waited about 24 hours until trying anything again....neither of those changed anything...
Is there anything else I can try besides throwing it against a brick wall?
I'd really like something to completely wipe/format/repartition the tablet completely back to factory and start over......
Getting APX mode to function is not a problem......so I can NVFlash it but what I've tried so far has not worked (it doesn't delete the data partition, etc..as I reflash and it's right where it was before I turned it off).
Windows or Ubuntu methods are fine....I'd just like to get this tablet functional again.
Your tablet is bricked
I`m sorry to be the bearer of bad news, but im afraid your tablet has been bricked, meaning that irreversible damage has been done to your device after tampering with it. Any wrong steps and your device becomes a paperweight. You have now choice but to get a new tablet or phone. You cant send that in for repair as flashing a custom rom would have voided your warranty, sorrry
With APX mode still accessible I do not believe the tablet is "bricked" at this point.
Something is preventing it from "booting" normally though it can boot after an nvflash.
you are using nvflash to install a temporary firmware onto your device. however, the original firmware on you device has been damaged beyond repair and the only solution is to use a hardware debug board and hook it up to somewhere in the motherboard of your tab and do stuff even i dont know how to.
that is the meaning of bricked!!!
tcrews said:
With APX mode still accessible I do not believe the tablet is "bricked" at this point.
Something is preventing it from "booting" normally though it can boot after an nvflash.
Click to expand...
Click to collapse
Hi,
Did you look through this thread:
http://forum.xda-developers.com/showthread.x?t=865058&highlight=stuck+apx&page=2
Sorry to hear about your plight ...
One of the suggestions there was, after you NVflashed to stock, to install Z4root and then root it. There was another post about holding both volume + and - while powering on.
I kind of agree that if you can NVflash, you should be able to unbrick-ify it. If none of those things work, maybe roebeet or rothnic can help?
Sorry if this is not too helpful...
Jim
P.S. Question: Are you sure/do you know if you might have one of those few "320" units, the ones with the 1GB RAM instead of the 512MB RAM? I seem to recall that roebeet said that those are partitioned differently, and that the stock NVflash wouldn't work with them, so maybe that might explain why? Just a thought...
IT IS NOT BRICKED. You need to go to the development forum and read about nvflashing all partitions back to stock. As long as you can get into apx mode you haven't bricked it. Most likely your partitions are screwed up. Yoour recovery partition seems to be wiped and possibly your boot partition too. Your tab doesnt know what to do when you turn it on so it goee to apx. There is a thread in devekopment that shows you how to go back to stock with all partition
HERE IS THE LINK
http://forum.xda-developers.com/showthread.php?t=861950
siidheesh said:
I`m sorry to be the bearer of bad news, but im afraid your tablet has been bricked, meaning that irreversible damage has been done to your device after tampering with it. Any wrong steps and your device becomes a paperweight. You have now choice but to get a new tablet or phone. You cant send that in for repair as flashing a custom rom would have voided your warranty, sorrry
Click to expand...
Click to collapse
WRONG!
rayden25 said:
WRONG!
Click to expand...
Click to collapse
With what little I know (still learning) about the Gtab, I agree with what rayden and some others have said. The Gtab is probably one of the few (maybe the only one) tablets that have the tools to be "almost" unbrickable.
Just about the only thing that is not there is a JTAG port (and there's probably one there that hasn't been unearthed).
Hopefully we aren't all wrong about that ...
JMHO...
Jim
You really dont need a jtag because of the apx mode. Apx is almost like jtag in a sense, it gives you direct access to flash what you need to. Thats why his tab will boot the one time but something else is borked up. The more i think about it the more i feel he has a messed up recovery partition or boot partition. He was playing with clockwork when this all started which gets flashed to recovery. If he flashes a stock recovery partition he should be good.
Oh make sure to take any update.zip off sdcard so when you do get recovery back it doesnt flash something else.
Yea that sux dude. I be worried when I'm flashing roms of this happening. Sum ppl flash just anything just to do it.
Sorry about ur device..
Sent from my HTC Vision using XDA App
Tcrews,
BTW, there's also an IRC channel where some folks hang out:
http://forum.xda-developers.com/showthread.php?t=888465
If someone's there they might help.
Jim
jimcpl said:
Hi,
Did you look through this thread:
http://forum.xda-developers.com/showthread.x?t=865058&highlight=stuck+apx&page=2
Click to expand...
Click to collapse
Yep, that got me flashed back to a stock image and even to a TnT-lite 1.02 image. Still not able to boot without flashing first.
jimcpl said:
Hi,
One of the suggestions there was, after you NVflashed to stock, to install Z4root and then root it. There was another post about holding both volume + and - while powering on.
Click to expand...
Click to collapse
Tried that as well. At end of root it asks to reboot, and then I'm back to having to use NVflash to bring it back up.
jimcpl said:
Hi,
P.S. Question: Are you sure/do you know if you might have one of those few "320" units, the ones with the 1GB RAM instead of the 512MB RAM? I seem to recall that roebeet said that those are partitioned differently, and that the stock NVflash wouldn't work with them, so maybe that might explain why? Just a thought...
Click to expand...
Click to collapse
I just checked the back, model is UPC300-2 2.
I'll keep playing. Someone posted in another thread here that they had the same issue (having to use nvflash to boot) but then posted they fixed it (but without what they did other than using ADB). I've PM'd them to see exactly what they did so I'm hoping they respond.
tcrews said:
Yep, that got me flashed back to a stock image and even to a TnT-lite 1.02 image. Still not able to boot without flashing first.
Tried that as well. At end of root it asks to reboot, and then I'm back to having to use NVflash to bring it back up.
I just checked the back, model is UPC300-2 2.
I'll keep playing. Someone posted in another thread here that they had the same issue (having to use nvflash to boot) but then posted they fixed it (but without what they did other than using ADB). I've PM'd them to see exactly what they did so I'm hoping they respond.
Click to expand...
Click to collapse
Sorry to hear all that ... Can you post back as you progress, as it might be helpful to others here. Also, have you tried the IRC channel, to see if there's anyone there that might be able to help?
Jim
Dude, TNT Lite does not have a recovery partition in it. That's why it's not "sticking". You need to update with something with the recovery partition in it. None of the custom roms flash the recovery partition. You need to use one of the stock roms direct from viewsonic or nvflash from the link I posted. Trust me. It will work.
rayden25 said:
Dude, TNT Lite does not have a recovery partition in it. That's why it's not "sticking". You need to update with something with the recovery partition in it. None of the custom roms flash the recovery partition. You need to use one of the stock roms direct from viewsonic or nvflash from the link I posted. Trust me. It will work.
Click to expand...
Click to collapse
I've done all that...I thought I had mentioned it in the first post...
Basically I can NVFlash anything, but power off or attempt a reboot and nothing...until I nvflash again.
I started with the stock images...then NVFlash of TnT-lite 1.02 (which includes Clockworkmod), then threw in the system.img from the latest TnT.....nothing "sticks".
I'll flash the stock TnT and get an update notification that 1.1-3389 is available....download that....and when it reboots to install.....nothing. Have to flash again something to get it to boot. Also if I don't download the update and just power off or install something that forces a reboot....nothing.
It's very close to being used for target practice now....
(it's downloading 1.1-3389 again since I just did another nvflash
(below is what I get every time I nvflash)
[email protected]:~/NVFlash/tegra_froyo_20101105$ ./nvflash_gtablet.sh
Flashing G Tablet with base images...
[sudo] password for snkbitten:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x17144042441fe1d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Done!
Click to expand...
Click to collapse
and as an "just now" update...accepting the install of 1.1-3389 shuts down and leaves it down and unable to boot until I nvflash.
I just noticed above (and while doing it a few times just now) it formats 2 and 3 but doesn't send the images...it starts with sending file: part4.img
Anyone know what partitions BCT and PT are?
the gtablet.cfg file has them with part2.img and part3.img which are in the same folder with the other images..
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part2.img
[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part3.img
tcrews said:
I just noticed above (and while doing it a few times just now) it formats 2 and 3 but doesn't send the images...it starts with sending file: part4.img
Anyone know what partitions BCT and PT are?
the gtablet.cfg file has them with part2.img and part3.img which are in the same folder with the other images..
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part2.img
[partition]
name=PT
id=3
type=partition_table
allocation_policy=sequential
filesystem_type=basic
size=131072
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part3.img
Click to expand...
Click to collapse
I think that this has a partition layout info:
http://tosh-ac100.wetpaint.com/page/Partition+Layout
BCT = boot configuratin table
PT = partition table
Jim
I'm sorry, I didn't understand that you did a full NVFLASH restore, but something obviously still isn't right. I am 100% confident the device is not bricked. It just needs to have a full restore and it should be good.
Where did you get the recovery files from? How are you running them? Windows or
Linux?
I am commited to getting this thing to work again. It's a challenge that has me thinking like crazy!
rayden25 said:
I'm sorry, I didn't understand that you did a full NVFLASH restore, but something obviously still isn't right. I am 100% confident the device is not bricked. It just needs to have a full restore and it should be good.
Where did you get the recovery files from? How are you running them? Windows or
Linux?
I am commited to getting this thing to work again. It's a challenge that has me thinking like crazy!
Click to expand...
Click to collapse
Oh...it's already drove me crazy!
I got them from the same thread you had linked.
I've done it on both Windows 7 (64 bit and 32bit) and Ubuntu 64bit 10.04.
It's frustrating in that it boots after the flash, everything works but I can't power it off or reboot it.
Once it shuts down....it's down. Screen doesn't flash from pressing power....no recovery to boot in to (stock or otherwise)....just plug it in and either nothing (then press volume - and power and watch for USB activity as the screen doesn't flash or anything) and then I can nvflash to it.
Once I nvflash and boot...I can adb access it, use wifi, etc....but that's it.
Related
Hi everyone
Thank you for looking into my problem which is:
I got a viewsonic 10s tablet working on android
it was working fine, i rooted using z4root and all is still OK.
The problem came when i tried to replace the libware files to enable the connected Arabic language, then after booting it will get stuck on the droid logo.
is there a way to re-flash the rom. i have not installed recovery yet and i could not boot in a recovery mode.
Any help would be appreciated.
Thanks in advance
Best regards
come on guys
More than 90 views and no one can direct me to the right choice
well, you posted in the viewpad 7 dev, not really the place to post these questions. I would help you, but don't know anything about the viewpad 10
it says viewpad 7 and variants. i suppose it is the same, isnt it.
i did not find viewpad 10
This is still the development forum, which is only supposed to be used for posts about new software development, try asking this in general.
Maybe some admin can move the thread ?
Amalgation said:
This is still the development forum, which is only supposed to be used for posts about new software development, try asking this in general.
Maybe some admin can move the thread ?
Click to expand...
Click to collapse
Did you manage to fix the problem?
My Viewpad is bricked. Cannot boot it anymore.
When I to install a new rom i get the following error
Code:
sending file: bootloader.bin
| 941512/941512 bytes sent
bootloader.bin sent successfully
sending file: recovery.img
\ 5064704/5064704 bytes sent
recovery.img sent successfully
sending file: boot.img
\ 4311040/4311040 bytes sent
boot.img sent successfully
sending file: system.img
/ 3145728/120449472 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
Press enter to continue:
I really hate to be writing this but could someone help me with restoring recovery? I successfully completed backing up with nvflash and have blob.bin, bricksafe.img, unlock-token.img, factory-config.img, recovery.bct, etc. I then tried following the instructions for Androwook JB and got to the point of flashing the official update when it froze up and now it is stuck in a bootloop. Holding power+down gives me
Code:
AndroidRoot 9.4.2.26r01
Android cardhu-user bootloader <2.10e> released by WW_epad-9.4.2.26-20120525 A03
Booting recovery kernel image
and holding power+up gives me apx mode. In apx mode I restored blob and bricksafe, but I am not sure how to go about restoring recovery with only apx available. I have tried using fastboot commands, but of course they don't work in apx mode. I know my way around this thing usually and was read up on issues and procedures but the crash during install really threw a monkey wrench into things...
Any help would be greatly apprciated!
Looks like the same problem I had. Try this http://forum.xda-developers.com/showpost.php?p=31858100&postcount=435
pbezza said:
Looks like the same problem I had. Try this http://forum.xda-developers.com/showpost.php?p=31858100&postcount=435
Click to expand...
Click to collapse
Yep! Didn't see your post, but that is exactly what I did, except I used the twrp.blob from team win's site. From there I was able to get back on track and successfully got Hairy Bean installed. Forgot though that it would completely wipe the tablet X( Oh well... Thanks for your reply. There is very little on restoring nvflash backups.
silentheero said:
There is very little on restoring nvflash backups.
Click to expand...
Click to collapse
Agreed. I was stoked when I used NVFlash to backup required files but when I had to recover my prime I thought "What do I do now, where are the the instructions to fix this?". Good to know it works with the twrp.blob file as well, I'll have to add that to my personal howto.
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.
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.
Hello
Seems like my LeMax2 is hardbricked.
Current Situation
Mobile starts with double vibrate, loads splash screen, waits for like 10 second and restarts again.
I can only enter into fastboot mode and QIFL Download mode.
What I have tried already with no success
QIFL Fastone restore
Full format with all partition tables
Installed almost all roms available via fastboot
Installed almost all recoveries but if entering into recovery it only shows splash of recovery with Leeco logo and restarts again.
Discharged mobile for a day
Kept it charging for a day
One of expert from XDA also helped with Teamweaver for almost 4 hours but no success.
I have been told the last thing I can try is if someone can give me a full diskdump of their own working LeMax2 829 preferably stock then it may work, this is the last thing I want to spend my time on before throwing it away and buying a new phone, my own guess is that partition table is corrupted or rom have bad sector so if anyone can help please I will be extremely thankful.
you have tried to unbrick with qfil service rom like it is described here:
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
???
I had the same situation and it worked for me!
He tried everything, really! This is stuff for an expert or anyone who run into the same Problem and was able to fix it. Maybe writing a full dd image (meanig really everything, not only some files|partitions) will do it. imei and mac adresses will be blanked of course. This is not about pulling files or partitions, its dumping the whole flash content to one file!
So: DD image needed badly, best same model, untinkered.
Another question:
Can somebody tell how to recreate the partition table properly? i mean not erasing content or formatting - recreating|repartitioning.
I know how it works on Samsung but it's totally different.
My thoughts are:
-Messed up partition table
-flash either physically defective or somehow Locked for read-only
-other Hardware/Software fault
I already threw one x829 away which had almost the same Problem.
I bet there will be more threads about malfunctioning x829 soon...
Gesendet von meinem Le X820 mit Tapatalk
---------- Post added at 02:41 PM ---------- Previous post was at 02:29 PM ----------
@craftvision, i have 1 (strange) idea. Today i received my spare x2 and while tinkering with the device, i made something stoopid wich could be of use...
Fixed it in 1 minute again but was surprised it worked...
Of course, chances are low...
Gesendet von meinem Le X820 mit Tapatalk
Yes we have tried everything and every possible way with QIFL too,
A.N.Droid said:
A.N.Droid
Click to expand...
Click to collapse
has spent his more than 8 hours of his personal time with me on Teamweaver, he is really a good helpful guy and a real Android expert, big thanks to him for all his time.
Phone is still in same condition, only loads splash for 10 seconds and restarts and enters only in QFIL Download or Fastboot mood, all installations are still successful, seeings new Splash screens with every rom that I could install via fast but but boot loop and no recovery.
craftsvision said:
Yes we have tried everything and every possible way with QIFL too, has spent his more than 8 hours of his personal time with me on Teamweaver, he is really a good helpful guy and a real Android expert, big thanks to him for all his time.
Phone is still in same condition, only loads splash for 10 seconds and restarts and enters only in QFIL Download or Fastboot mood, all installations are still successful, seeings new Splash screens with every rom that I could install via fast but but boot loop and no recovery.
Click to expand...
Click to collapse
Happened to me with a Oneplus One. Rarely it booted but it had random reboots on every rom from minute to minute. My guess is that something is fuc*ed up inside the phone. Never found a solution, just bought a new motherboard. My guess was that the EMMC or something broke
craftsvision said:
Hello
Seems like my LeMax2 is hardbricked.
Current Situation
Mobile starts with double vibrate, loads splash screen, waits for like 10 second and restarts again.
I can only enter into fastboot mode and QIFL Download mode.
What I have tried already with no success
QIFL Fastone restore
Full format with all partition tables
Installed almost all roms available via fastboot
Installed almost all recoveries but if entering into recovery it only shows splash of recovery with Leeco logo and restarts again.
Discharged mobile for a day
Kept it charging for a day
One of expert from XDA also helped with Teamweaver for almost 4 hours but no success.
I have been told the last thing I can try is if someone can give me a full diskdump of their own working LeMax2 829 preferably stock then it may work, this is the last thing I want to spend my time on before throwing it away and buying a new phone, my own guess is that partition table is corrupted or rom have bad sector so if anyone can help please I will be extremely thankful.
Click to expand...
Click to collapse
Instead of throwing it away, please send it to me, pay your shipping ......
I was going to say the same thing here do not throw it away, I own a x829 for about one week and love this thing.
Yes, try replacing the whole memory block. That would be the best way to rule out hardware fault.
Tushar1 said:
Yes, try replacing the whole memory block. That would be the best way to rule out hardware fault.
Click to expand...
Click to collapse
I think we cannot even buy only memory block, I guess I have to buy complete mother board, and so far I could not even find a complete motherboard set online anywhere.
theese bga's are not easy to exhange. best would be an infrared reworkstation with ir preheater. if you aren't familiar with bga reballing, i think the chance you get it right is under 1%.
i have a cheap hot-air solder station, self made preheater, ir-thermometer, thermo-couple and lot of required tools. the equipment is sufficient to do simple reflows on xbox, playstation, whatever electronics... however, this is not a professional fix and not sufficient to do bga reballings. you need to follow a temperature curve, it's tricky (for me at least). you can try to put it in the oven with no-clean flux but chances are high you will ruin it. plastic melts easily, capacitors tend to "popcorn" when too much/too long heat is apllied.
Gesendet von meinem Le X820 mit Tapatalk
Is there a way to convert a Recovery rom to a fastboot rom?
I tried this method
http://www.droidviews.com/convert-and-extract-system-img-and-system-new-dat-files-on-windows/
That converted system.new.dat to system.img but while flash it gives this error "Invalid sparse file format at header magi" and then fastboot command crashes..!
I want to convert CN26 flash able via fastboot because it was most successful rom for me so far!
craftsvision said:
Is there a way to convert a Recovery rom to a fastboot rom?
I tried this method
http://www.droidviews.com/convert-and-extract-system-img-and-system-new-dat-files-on-windows/
That converted system.new.dat to system.img but while flash it gives this error "Invalid sparse file format at header magi" and then fastboot command crashes..!
I want to convert CN26 flash able via fastboot because it was most successful rom for me so far!
Click to expand...
Click to collapse
craftsvision said:
I think we cannot even buy only memory block, I guess I have to buy complete mother board, and so far I could not even find a complete motherboard set online anywhere.
Click to expand...
Click to collapse
No I didn't mean that you should buy emmc(the flash storage) or the motherboard. I meant the whole partition dump of a working device. I won't be able to find a le max 2, but I can help you with the flashing. The header sparse thing means it needs to be in sparse chunks or even the sparse header at the top of the image file. The file is bigger than what your device supports, so it will send it out in chunks. Sometimes it automatically starts after waiting for a few minutes. It would be much easier to just flash it by TWRP. Have you tried flashing recovery partition or directly booting to twrp from the fastboot bootloader screen?
Tushar1 said:
No I didn't mean that you should buy emmc(the flash storage) or the motherboard. I meant the whole partition dump of a working device. I won't be able to find a le max 2, but I can help you with the flashing. The header sparse thing means it needs to be in sparse chunks or even the sparse header at the top of the image file. The file is bigger than what your device supports, so it will send it out in chunks. Sometimes it automatically starts after waiting for a few minutes. It would be much easier to just flash it by TWRP. Have you tried flashing recovery partition or directly booting to twrp from the fastboot bootloader screen?
Click to expand...
Click to collapse
Yes, have tried flashing all recoveries available in recovery partition or even in boot partition. A.N.Driod has also flashed his own x829 diskdump on my phone but no success.
Only fastboot and QIFL Download is available at this phone...
craftsvision said:
Yes, have tried flashing all recoveries available in recovery partition or even in boot partition. A.N.Driod has also flashed his own x829 diskdump on my phone but no success.
Only fastboot and QIFL Download is available at this phone...
Click to expand...
Click to collapse
Are you able to boot into some image through fastboot? Like, "fastboot boot recovery.img"
Tushar1 said:
Are you able to boot into some image through fastboot? Like, "fastboot boot recovery.img"
Click to expand...
Click to collapse
no, flash is success but loads only splash of recovery, waits for 10 seconds and reboots again. Have tried all versions of TWRP available
Don't flash recovery, you can directly boot from the fastboot screen. Instead of "fastboot flash recovery twrprecovery.img" do "fastboot boot twrprecovery.img".
Tushar1 said:
Don't flash recovery, you can directly boot from the fastboot screen. Instead of "fastboot flash recovery twrprecovery.img" do "fastboot boot twrprecovery.img".
Click to expand...
Click to collapse
That too negative, it loads normal splash and then restarts
And you have tried flashing stock sparse images with qfil?
Tushar1 said:
And you have tried flashing stock sparse images with qfil?
Click to expand...
Click to collapse
if you are talking about exactly this method then yes done 100 times already
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
craftsvision said:
if you are talking about exactly this method then yes done 100 times already
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
Click to expand...
Click to collapse
There is probably a hardware problem with the device. The internal storage should be ok as the qfil flashing should fail and the device would not boot in any way if that was the case.
If you have successfully flashed through qfil, there is no reason for a boot problem...
---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------
Btw, the above link you provided is for x820 which is 32 gb version, i think. X829 is 64 gb, maybe try this? https://forum.xda-developers.com/le-max-2/how-to/official-fastboot-rom-x829-regular-twrp-t3620591