Related
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
mrchew1982 said:
My gtab starts up and displays the viewsonic logo but will not boot into the ROM and will not boot into recovery mode.
when it is powered on normally the viewsonic logo appears and a black bar shows at the bottom of the screen a few seconds later.
power & volume+ show "detect a recovery key pressed" and "booting recovery kernal image". nothing more happens, even with a recovery image loaded onto the sdcard.
I am quite sure that i need to repartition, but i am at a loss of how to do so.
things that i have tried:
1.http://viewsonic-gtablet-for-dummies.webs.com/
tried everything, even the 'nuke from orbit' option of FORMAT_nvflash. tried both 1.1 and 1.2 images, would not boot into any stock recovery rom. tried holding the volume+ key during flash, still would not boot into recovery.
2. http://forum.xda-developers.com/showpost.php?p=12220001&postcount=1
same results as above.
3.http://forum.xda-developers.com/showthread.php?t=1091304
same.
I'm down to the point where i'm going to open it up to see if there is a loose connector or something.
anybody have a better idea?
Click to expand...
Click to collapse
It's not bricked.
No need to open at this point.
The links you have looked at are very good starting point.
you may need to put your tablet in APX mode to NVflash a recovery.
APX is power off. Power on with VOLUME (-) (not vol+) and hold until a black screen pops up.
If you have the correct drivers, your PC should recognize the tablet.
You can run the nvflash.bat at this point
I recommend using the method HERE. This is one of the ORIGINAL NVFlash posts for the GTab. I have also posted my own nvflash folder for windows users HERE there is both a 1.1 and 1.2 bootloader version up there.
APX mode blues
Thanks for the quick replies.
I have re-flashed the tablet using APX mode about 20 times already. Both 1.1 and 1.2 branches. With and without cwm. Multiple tries with each image to make sure that there wasn't an error.
I have used the "FORMAT" flash as well, received the mismatch error. flashed all four versions of roms (1.1, 1.1cwm, 1.2, 1.2cwm) after redoing the "FORMAT".
Still nothing. It hangs on the boot image. If I attempt to enter recovery mode it hangs after displaying the text. Even if I hold volume+ during flashing so that it will go directly into recovery mode after the flash.
I know that it is taking the flash, one of the images that I tried has the Tegra logo instead of the Viewsonic as the boot screen. NVflash completes every time without error.
I am really at the end of my rope here as I haven't been able to find anyone that couldn't get into recovery after flashing.
Thanks for the help, any further suggestions would be greatly appreciated!
p.s. I tried once more tonight using Roebeet's instructions and the NVflash Pixelrider provided just to make sure that i didn't miss a step. Still hanging on the boot screen...
Try this:
1. nvflash back to a stock ROM (1.1 or 1.2). I strongly recommend bekit's original 1.1 images.
2. power off before the gTab boots into the stock ROM you just nvflashed.
3. put gTab into APX mode and run this command:
Code:
C:\> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go[/B]
The tablet will try to boot into the stock ROM (for the first time).
still no luck!
Thank you very much for the reply. Something new to try! Unfortunately it still freezes up.
recap:
Downloaded the "bekit 1105" image (nvflash_windows_20100500.zip)from Roebeet's sticky and the windows version of nvflash. Unzipped both into a folder on my desktop. 30 files weighing in at 202MB. (ADX drivers for Windows7x64 were previously manually installed through Device Manager)
Started gtab with "volume-" button depressed. Screen flashed on with Viewsonic logo then flashed off. Attached usb cable. Heard connection sound from Windows.
Opened folder previously mentioned, double clicked nvflash_gtab.bat. Clicked "Run" on warning popup.
cmd.exe window pops up:
Code:
C:\Users\Desktop\Desktop\bekit1105>"nvflash.exe" --bct gtablet.bct --setbct --bl
bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
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
Press enter to continue:
(did not press key yet...)
turned gtab off using power button. Disconnected usb and pressed key to exit NvFlash_gtab.bat window.
Turned gtab on whilst pressing "Volume-". Screen flashes on then goes blank. Windows plays connect sound.
Ran command:
C:\Users\Desktop\Desktop\bekit1105>nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
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
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
Formatting partition 7 please wait.. done!
Formatting partition 12 please wait.. done!
C:\Users\Desktop\Desktop\bekit1105>
Click to expand...
Click to collapse
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Waited 10 minutes. powered off using button, disconnected USB. Powered back on, Viewsonic logo appears, black bar flashes onto bottom of the screen, and...
Nothing else happens!
Waited another 10 minutes. Tried to get into recovery mode using "Volume+", still hangs, even with an image on the microsd card. Tried the whole thing over again, still nothing.
The fact that it never reboots after nvflash has me worried that there is something deeply wrong. Is there a way that I could repartition and totally wipe it via nvflash?
This thing is stubborn! Still hoping to find a solution...
Thank you again for the help!
mrchew1982 said:
Tablet shows "Entering NvFlash recovery mode / Nv3p Server". Nothing else happens.
Click to expand...
Click to collapse
The ``--go'' parameter to nvflash will cause the bootloader to try to boot into the ROM after the requested actions complete. Without a ``--go'' parameter, the bootloader will wait to further commands and you'll have to power off. If the gTab did not boot into the ROM with ``--go'' then something is wrong.
BTW, does adb work in recovery mode? Run this command:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
and post that text file here if it was any output.
Right now it looks like I'll have to build a custom recovery for you to test things out. In the mean time, try the procedures in this post one by one. See if any of them help. And, stick to bekit's recovery until we resolve this.
Thank you!
Thank you!
I will setup adb later tonight and give it a try. I was reading up on it elsewhere. It will be interesting to see if it responds.
Would hitting the reset button on the motherboard do any good? I have opened the case before to re-solder the power connector...
Thank you, can't say that enough!
mrchew1982 said:
Would hitting the reset button on the motherboard do any good?
Click to expand...
Click to collapse
Try it.
I have opened the case before to re-solder the power connector...
Click to expand...
Click to collapse
Hmm. Now this can't be coincidence, can it? User raywaldo on this board is reporting the same problem after he soldered wires to fix his loose connector. See this thread where I mention this.
Ordinarily, based on the symptoms, I would've said that this was a bootloader incompatibility problem. But, both of you have done a full nvflash, so that's out. I'm leaning towards a HW fault right now, but, we'll need more data to make a definitive determination.
As I said, try out the other procedures first (and don't have a micro SD card with the CWM update file in it while you're doing those procedures--the stock recovery will try to install update.zip files if it finds them; CWM will not). If none of them work, then I'll send you a custom recovery image which will let us know if the bootloader did actually load and run the recovery/std kernel.
no adb. reset didn't change anything.
Thank you for sticking with me rajeevvp.
I installed the android sdk (and JDK) per the instructions:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
I used SDK manager to download the platform tools and the google usb driver. Followed the instructions to uninstall the NvFlash driver and installed it as a composite ADB per the instructions. When i started the tablet normally it loads the usb storage device drive and assigns it drive letter E: (which never shows up in "My Computer" and says "Device not ready" from cmd prompt).
It would only connect as an ADB device when i put it into APX mode, which i don't think is right...
It showed up under USB deview, but said that the driver was winusb.sys, which doesn't sound right to me either...
used the echo command, ran "adb kill-server" and "adb devices". it didn't show anything connected.
next i tried the command that you posted and it said "access is denied".
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
I am looking for damage on the PCB but haven't found any yet. I will desolder the power connector later tonight and give it a bath in some PCB cleaning spray.
Thanks for your help once again!
mrchew1982 said:
so i went the other route and popped the case back open. tried all four methods for hardware reset (unplugging battery, shorting capacitors, reset button and shorting the four solder pads), no change in behavior...
Click to expand...
Click to collapse
Try that adb command on Linux; Windows is too much pain--don't want to troubleshoot an "ADB is not working" problem too.
The link from wroark is interesting. I am leaning towards hardware damage as well because i have never gotten a complete boot out of it since the repair. Maybe i bungled something up, and only made it worse with the flashing...
Click to expand...
Click to collapse
Go through this thread as well.
OK. Now for some troubleshooting.
1. Remove any external microSD cards, as always.
2. Put gTab into APX mode and run this command:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go[/B]
This will format all the problemmatic partitions and then upload CWM-2.5.1.1-bekit-0.8 with a different kernel onto both the "recovery" and "boot" partitions. The kernel has been modified to print boot-up messages as it does on standard Linux. If the bootloader loads and runs either kernel ("boot" or "recovery") then you should see, first, the 2 penguins logo (one for each processor), and then, the kernel messages below that. After the kernel finishes, /init will run, clear the screen, and print "ANDROID" in small caps, and then CWM should start.
3. Use the bootloader.bin--which is from 1.1-3588, the last VS 1.1 update--and the recovery.img in the zip attachment.
surgery done...
I wasn't happy with the solder joints that I laid on last time, it looked like I might have bridged two of the pads... so I removed the power connector completely only to find that the housing was split down the middle. Found a new connector (perfect match here: http://www.dcpowerjacks.net/catalog/index.php?main_page=product_info&cPath=15&products_id=202), got it today. Cleaned the pads and carefully connected the new one. sprayed everything clean, it looked great afterwords, but no change in behavior... I didn't see anything loose or missing either when I went over it with the magnifying glass.
Ok, reflashed per your instructions. here is the output:
Code:
C:\Users\Desktop\Desktop\bekit1105>nvflash --bl bootloader.bin --format_partition 7 --format_partition 8 --format_partition 9 --format_partition 10 --format_partition 12 --download 9 recovery.img --download 10 recovery.img --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714118842bf5057
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
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928940/928940 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Formatting partition 7 please wait.. done!
Formatting partition 8 please wait.. done!
Formatting partition 9 please wait.. done!
Formatting partition 10 please wait.. done!
Formatting partition 12 please wait.. done!
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
sending file: recovery.img
| 3598336/3598336 bytes sent
recovery.img sent successfully
C:\Users\Desktop\Desktop\bekit1105>
It rebooted into the screen that you described but stopped short of going into clockwork. for a long time the last lines were:
Code:
19.213803 so340010_kbd: probe of so340010_kbd failed with error -1
19.217161
19.217164 I2C Slave is *New*
19.820563 NvOdmMouseDeviceOpen failed
20.019509 android_usb Gadget: high speed config #1: android
I then heard the USB connection sound and windows notified me that a USB storage device had been installed (no drive shows up in "My Computer").
Then it started reprinting an error message about every 5 minutes:
Code:
257.010389 INFO: task cpufreq-dvfsd:286 blocked for more than 120 seconds.
257.013674 "echo 0 > /proc/sys/kernal/hung_task_timeout_secs" disables this message.
257.016995 cpufreq-dvfsd D c050ac38 0 286 2 0x00000000
{continued from reboot}
246.807349 Backtrace:
246.810534 (<c050a11c>) (schedule+0x0/0xc18) from (<c00e1680>) (kthread+0x70/0x90)
246.813892 (<c00e1610>) (kthread+oxo/0x90) from (<c00c8498>) (do_exit+0x0/0x73c)
246.817285 r7:00000000 r6:00000000 r5:0000000 r4:0000000
366.817615 INFO: {then it repeats verbatim}
After repeating 3-4times then it goes to a page with just a bunch of numbers inside of parenthesis on the left hand side (counter overran the buffer?) and no text on the right.
When I rebooted it without the USB attached the last message shown is "NvOdmMouseDeviceOpen failed" before it went into the "INFO" error messages.
Still think its a hardware problem?
I will get a linux boot CD setup to try ADB mode again, but i'm hoping that the messages above will be enough to figure this out.
Thank you, once again, for your time and help.
pictures...
Just in case I missed something, I attached some screenshots.
they are in chronological order, 989 is before the "INFO:" error messages pop up, 990 shows those error messages, and 991 is the final screen with no messages.
Thanks for the screenshots. Judging from the visible kernel messages, this looks very much like a hardware fault. The "so340010_kbd" is the driver for the soft keys to the right of the display. The error messages indicate a failure to communicate with the controller for those soft-keys.
I suggest that you start at those soft-key pads and trace the lines back to their controller chip then scrutinize the circuit traces from this chip all the way back to the CPU. See if everything looks OK.
Try ADB on Linux, but, I don't hold out much hope for getting anything out of it: The kernel looks like it is having serious problems with the hardware--I don't think it has even got around to starting up the user-land processes. And, don't worry about the INFO messages relating to cpufreq-dvfsd. You can disregard them for the moment.
EDIT: A thought just struck me. It's winter-time over there, right. Did you take the proper precautions while handling the board? It's very easy to fry a chip silently this time of the year over there using ESD: walk on the carpet, pick up a load of static electricity, then toast something with a simple touch. I borked a board like that one time I was there.
bricked
i have been having same problems with my g-tab, i tried the modified recovery and was able to get to clockwork. i tried updating to few roms, i have NVflashed 100 times. Everytime i NVflash, it shows the tapNtap boot screen, it cycles through this for 4 to 5 times, then just shuts off. Then i try to start again, get nothing, can only go into APX mode which i can only do NVflash and just does same thing. So i tried the modified recovery, goes to clockwork and tried installing other roms, installs without problem, but when restart system will not boot at all. Just black screen and can only do APX mode... also tried opening case unplugging battery, pressing reset button on motherboard... i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
theterminator69 said:
i have been having same problems with my g-tab,...
Click to expand...
Click to collapse
If you can boot into CWM and install ROMs, then you don't have the same problem. And, that modified CWM was meant to be a diagnostic aid--it was not intended to be a cure for gTab illnesses.
i think the internal SD needs to be completely wiped and no matter what tool i have used, there is still data there.
Click to expand...
Click to collapse
Is the data still there after you "Partition SD card" in CWM? Make sure you remove any external microSD cards from the tablet first.
well this thread is created by meh to help noobs get root,recovery,roms for ur devices ...
SEARCHED THE WHOLE NET AND GOOGLED BUT STILL CANT GET UR PHONE"Z ROM?? THEN UR AT THE RIGHT PLACE ...
I WILL HELP YOU TO FIND THE CORRECT ROM,RECOVERY FOR YOUR PHONE
ENTER BELOW YOUR PHONES MODEL WITH CORRECT MANUFACTURES ROM AND IL FIND AND GVE YU
HOPE I CAN HELP A LOT OF NOOBS
For Walton Primo H1 [a Chinese rebranded smartphone]
I need help with updating Android version and installing custom ROM. Let me explain in detail.
I have a Chinese made rebranded Android smartphone which is Walton Primo H1. This phone runs on Android 4.1.2 JellyBean. I want to upgrade the version to the latest possible one and want to install a custom ROM so that my experience with the phone gets a little better. But unfortunately there are no ROMs available out there and I don’t expect that there will be any. Is there any possibility of upgrading my Android version/install ROM? If yes then can you suggest me which ROM will be suitable for the phone?
Short specification:
CPU: Quad-core 1.2 GHz Qualcomm Snapdragon S4
GPU: Andreno 203
Rear camera: 8 MP
Front camera: 2 MP
RAM: 1 GB DDR
ROM: 4 GB
Display: 4.7 inch OGS IPS
Resolution: 960 x 540 pixel
Let me know if you need any further information from me.
I posted the same post before in this forum but got no reply. I would highly appreciate your effort if you find me a ROM which may support by device. Thanks in advance.
mehedihasan said:
I need help with updating Android version and installing custom ROM. Let me explain in detail.
I have a Chinese made rebranded Android smartphone which is Walton Primo H1. This phone runs on Android 4.1.2 JellyBean. I want to upgrade the version to the latest possible one and want to install a custom ROM so that my experience with the phone gets a little better. But unfortunately there are no ROMs available out there and I don’t expect that there will be any. Is there any possibility of upgrading my Android version/install ROM? If yes then can you suggest me which ROM will be suitable for the phone?
Short specification:
CPU: Quad-core 1.2 GHz Qualcomm Snapdragon S4
GPU: Andreno 203
Rear camera: 8 MP
Front camera: 2 MP
RAM: 1 GB DDR
ROM: 4 GB
Display: 4.7 inch OGS IPS
Resolution: 960 x 540 pixel
Let me know if you need any further information from me.
I posted the same post before in this forum but got no reply. I would highly appreciate your effort if you find me a ROM which may support by device. Thanks in advance.
Click to expand...
Click to collapse
BRO AT THIS VERY MOMENT ...ONLY ROOT AND CWM ARE AVILABLE FOR Walton Primo H1... IF YU WANT I CAN YU DERE LINK... one of my frnd own dis device... he iz working on PERFORMANCE BASED ROM FOR THIS PHONE...IF HE GETS SUCCEED...HE WIL UPLOAD IT..AND IL INFORM YOU ABOUT THE DETAILS ...hope i help you
Thanks a lot.
siva aggzz said:
BRO AT THIS VERY MOMENT ...ONLY ROOT AND CWM ARE AVILABLE FOR Walton Primo H1... IF YU WANT I CAN YU DERE LINK... one of my frnd own dis device... he iz working on PERFORMANCE BASED ROM FOR THIS PHONE...IF HE GETS SUCCEED...HE WIL UPLOAD IT..AND IL INFORM YOU ABOUT THE DETAILS ...hope i help you
Click to expand...
Click to collapse
At least now I know that there is no suitable ROM for my device and I can stop searching for that. Thanks a lot for the reply.:good:
I did anyhow rooted my device but didn't found any CWM. Please send the link to me.
HTC Desire VC
Dual GSM and CDMA.
Is there any custom JB ROM available?
Already rooted with CWM Recovery
Thanks in advance
mehedihasan said:
At least now I know that there is no suitable ROM for my device and I can stop searching for that. Thanks a lot for the reply.:good:
I did anyhow rooted my device but didn't found any CWM. Please send the link to me.
Click to expand...
Click to collapse
GO TO THIS THREAD..IT CONTAINS THE TUTORIAL ALSO ..
http://forum.xda-developers.com/showthread.php?p=46732931
BEST OF LUCK ...DONT FORGET THE THANKS BUTTON
Would you help me on this one?
I was modding my stock rom of W35. In the updater script, got a bit problem...
it says:
Code:
format("ext4", "EMMC" /dev/block/mmcblk0"", "MTD", "system");
mount("ext4", "EMMC" /dev/block/mmcblk0"", "MTD", "system", "/system");
format("ext4", "EMMC", "/dev/block/mmcblk0p2"", "MTD", "cache");
package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
mount("ext4", "EMMC", "/dev/block/mmcblk0p3", "/data");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
show_progress(0.200000, 20);
mount("ext4", "EMMC", "/dev/block/mmcblk0", "/system");
package_extract_dir("system", "/system");
But cat /proc/Dumchar_info
Code:
[email protected]:/ $ cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000025800000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000001ae00000 0x00000000275e4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000032000000 0x00000000423e4000 2 /dev/block/mmcblk0p3
fat 0x000000007221c000 0x00000000743e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
and Cat /proc/partitions
Code:
[email protected]:/ $ cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd
dsp_bl 0x00000000005c0000 0x0000000000040000 2 /dev/misc-sd
mbr 0x0000000000004000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x000000000005c000 0x0000000000004000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000060000 2 /dev/block/mmcblk0
nvram 0x0000000000300000 0x0000000000460000 2 /dev/block/mmcblk0
seccfg 0x0000000000020000 0x0000000000760000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000000780000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x00000000007e0000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000000de0000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x00000000013e0000 2 /dev/block/mmcblk0p5
misc 0x0000000000060000 0x00000000019e0000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000001a40000 2 /dev/block/mmcblk0
expdb 0x00000000000a0000 0x0000000001d40000 2 /dev/block/mmcblk0
ebr2 0x0000000000004000 0x0000000001de0000 2 /dev/block/mmcblk0
android 0x0000000025800000 0x0000000001de4000 2 /dev/block/mmcblk0p6
cache 0x000000001ae00000 0x00000000275e4000 2 /dev/block/mmcblk0p2
usrdata 0x0000000032000000 0x00000000423e4000 2 /dev/block/mmcblk0p3
fat 0x000000007221c000 0x00000000743e4000 2 /dev/block/mmcblk0p4
bmtpool 0x0000000000a00000 0x00000000ff9f0050 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
cat /proc/emmc
Code:
[email protected]:/data $ cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000020 00000002 "ebr1"
emmc_p2: 0013af20 000d6800 "cache"
emmc_p3: 00211f20 0018f800 "usrdata"
emmc_p4: 003a1f20 003910e0 "fat"
emmc_p5: 00009f00 00002800 "sec_ro"
emmc_p6: 0000ef20 0012b800 "android"
Would you like to help me out to determine the blocks that should be erased/formatted? It'll be quite helpful for me to cook one Custom ROM for W35. Any kinda Help is appreciated.
dokie80 said:
HTC Desire VC
Dual GSM and CDMA.
Is there any custom JB ROM available?
Already rooted with CWM Recovery
Thanks in advance
Click to expand...
Click to collapse
no custom roms based on jb are available for ur device..
but custom roms based on ics 4.0.3 are available bro
Abirwebster said:
I was modding my stock rom of W35. In the updater script, got a bit problem...
Would you like to help me out to determine the blocks that should be erased/formatted? It'll be quite helpful for me to cook one Custom ROM for W35. Any kinda Help is appreciated.
Click to expand...
Click to collapse
bro i would like to help yu out..but i m nt much familiar with blocks.. and so updater script... so m sorry
siva aggzz said:
bro i would like to help yu out..but i m nt much familiar with blocks.. and so updater script... so m sorry
Click to expand...
Click to collapse
it's okay,bro!..I've chosen to stick around the forums...
hello, i got some problems with my phone (freezes and restarts, sometime doesnt even want to turn on), so i tought that i need to re-flash soft so i'v download spflash and installed drivers but problem is that my PC doesnt detect my phone when there is no battery inside. When i connect phone to PC by USB cable nothing happens - device manager doesnt show any new device connected, also flash tool cannot start "Download" operation.
My phone is chinese TSD A9300 based on MTK6575
xPOGOx said:
hello, i got some problems with my phone (freezes and restarts, sometime doesnt even want to turn on), so i tought that i need to re-flash soft so i'v download spflash and installed drivers but problem is that my PC doesnt detect my phone when there is no battery inside. When i connect phone to PC by USB cable nothing happens - device manager doesnt show any new device connected, also flash tool cannot start "Download" operation.
My phone is chinese TSD A9300 based on MTK6575
Click to expand...
Click to collapse
Did you install the required drivers ??
SENT FROM MY LAVA IRIS 455 using xda developers app
siva aggzz said:
Did you install the required drivers ??
SENT FROM MY LAVA IRIS 455 using xda developers app
Click to expand...
Click to collapse
i dont think this is rly needed, windows should detect "SOMETHING" and it doesnt
xPOGOx said:
i dont think this is rly needed, windows should detect "SOMETHING" and it doesnt
Click to expand...
Click to collapse
Its needed... Wthout installing drivers... Yu can do nothing
Moreover remove the battery and den plug usb cable ... Ur pc will detect the mt 65xx preloader... But to succesfully let install the preloaders and all ul need the drivers..
Hit thanks instead of saying
siva aggzz said:
Its needed... Wthout installing drivers... Yu can do nothing
Moreover remove the battery and den plug usb cable ... Ur pc will detect the mt 65xx preloader... But to succesfully let install the preloaders and all ul need the drivers..
Hit thanks instead of saying
Click to expand...
Click to collapse
ok, i'll try to explain it one more time
The problem is that my PC does not detect my phone when i connect it without battery. So when phone is not detected i cant even install drivers, because my computer doesnt see any new device.
Try to help-me please!
I'm trying to raise the volume of my bluetooth phone unsuccessful..
This is what i tryed:
First I root my Nexus 4 with stock rom 4.3
I tryed Viper's 4 Android (newest version) with all configurations and modes (including install like user and like system app), nothing works...
I tryed Volume+, same, didnt work. In fact is lowering the volume. I can hear a fast loud volume (less the 1 second when I activate the boost) then back to limited volume :/
Then I install Franco.Kernel last version too. With headphones and speaker, the Franco boost works...
The I tryed everything again, V4A, Volume+ and NOTHING. The bluetooth phone still almost inaudible.
So, i was almost trying this FauxSound and then I read something what looks really bad in his description at play store:
"NOTE: DOES NOT BOOST/CONTROL BLUETOOTH... BLUETOOTH is 100% DIGITAL... THIS APP WILL NOT CHANGE BLUETOOTH VOLUMES OR GAINS!"
What this means? There is NO WAY to boost Bluetooth volume anymore???
I dont know what to do... Is anyway to do this? A really working way to boost the bluetoth phone volume? Or this is not possible?!
Anyone trying the same? Anyone has an Nexus 4 with 4.3 with this working?
Please help-me!
TNX A LOT!
siva aggzz said:
Its needed... Wthout installing drivers... Yu can do nothing
Moreover remove the battery and den plug usb cable ... Ur pc will detect the mt 65xx preloader... But to succesfully let install the preloaders and all ul need the drivers..
Hit thanks instead of saying
Click to expand...
Click to collapse
Take an other USB Port. Sometimes the phones don't like USB 3.0 or hubs. Or an other cable!?
Gesendet von meinem Xperia SP
joke19 said:
Take an other USB Port. Sometimes the phones don't like USB 3.0 or hubs. Or an other cable!?
Gesendet von meinem Xperia SP
Click to expand...
Click to collapse
other cable is the only thing i didnt tried yet, but it works perfectly when while phone is turned on...
xPOGOx said:
ok, i'll try to explain it one more time
The problem is that my PC does not detect my phone when i connect it without battery. So when phone is not detected i cant even install drivers, because my computer doesn't see any new device.
Click to expand...
Click to collapse
bro ... do this things..
first install the drivers... den connect ur device ... den only ur dvce will b detected ... cz mt 6575 devices have this issue ...
foxdanger said:
Try to help-me please!
I'm trying to raise the volume of my bluetooth phone unsuccessful..
This is what i tryed:
First I root my Nexus 4 with stock rom 4.3
I tryed Viper's 4 Android (newest version) with all configurations and modes (including install like user and like system app), nothing works...
I tryed Volume+, same, didnt work. In fact is lowering the volume. I can hear a fast loud volume (less the 1 second when I activate the boost) then back to limited volume :/
Then I install Franco.Kernel last version too. With headphones and speaker, the Franco boost works...
The I tryed everything again, V4A, Volume+ and NOTHING. The bluetooth phone still almost inaudible.
So, i was almost trying this FauxSound and then I read something what looks really bad in his description at play store:
"NOTE: DOES NOT BOOST/CONTROL BLUETOOTH... BLUETOOTH is 100% DIGITAL... THIS APP WILL NOT CHANGE BLUETOOTH VOLUMES OR GAINS!"
What this means? There is NO WAY to boost Bluetooth volume anymore???
I dont know what to do... Is anyway to do this? A really working way to boost the bluetoth phone volume? Or this is not possible?!
Anyone trying the same? Anyone has an Nexus 4 with 4.3 with this working?
Please help-me!
TNX A LOT!
Click to expand...
Click to collapse
bro yu can try this... frst going to engeenering mode den hardware den audio den select every ones volume to 160...
else try chngng the bluetooth ...but i guess the frst option will solve ur problem ...best of luck
I flashed a wrong rom, and now have phone N9006 mtk 6572 bricked, it gives this error now , dont turn on and connection takes few second,,
it gives this error now
Flash files count is :12
Action : Firmware update.
Selected Samsung Clone: Note 3 Clone(MT6572)
Phone must be off with battery inside.
Please insert USB cable now...
Detected : MTK USB Port (COM21)
Phone detected...Please wait
Sending DA agent, please wait...
Connect error: S_FT_ENABLE_DRAM_FAIL
Error connect phone, aborting.
All done.
I didnt make backup my fault, before that I read the info of phone which was stuck at logo, the info read via volcano box is this, can some one give a backup or any rom to at least revive this phone,
Version: V3.8
SN:xxxxxxxxxxx
Port:COM57
After format or Flash you have to press & hold power button for at least 1.30 mins.
Note for win7 users :
Start your Win 7 64bit with F8 key and choose 'Disable Driver Signature Enforcement'.
After that the spd drivers will have the ability to be loaded.
Available Ports:COM1 COM3 COM8 COM9 COM57
Current Port:COM57
Analysis of USB port,Please insert phone USB cable.
Connecting...
CPU TYPE:MT6572
Hardware version:CA01
Software version:0000
Boot downloading complete!
EMMC_ID:0x45010053454D3034472805A6827A513B
EMMC_PRODUCT_NAME: SAMSUNG :0x53454D303447
EMMC_BOOT1_SIZE: 0x00200000
EMMC_BOOT2_SIZE: 0x00200000
EMMC_PRMB_SIZE: 0x00200000
EMMC_GP1_SIZE: 0x00000000
EMMC_GP2_SIZE: 0x00000000
EMMC_GP3_SIZE: 0x00000000
EMMC_GP4_SIZE: 0x00000000
EMMC_USER_SIZE: 0x0EC000000(3.69 G)
Analysis of system files...
PRELOADER: addr:0x000000 --length:0x880000
MBR: addr:0x880000 --length:0x080000
EBR1: addr:0x900000 --length:0x080000
PRO_INFO: addr:0x980000 --length:0x300000
NVRAM: addr:0xC80000 --length:0x500000
PROTECT_F: addr:0x1180000 --length:0xA00000
PROTECT_S: addr:0x1B80000 --length:0xA00000
SECCFG: addr:0x2580000 --length:0x020000
UBOOT: addr:0x25A0000 --length:0x060000
BOOTIMG: addr:0x2600000 --length:0x600000
RECOVERY: addr:0x2C00000 --length:0x600000
SEC_RO: addr:0x3200000 --length:0x040000
MISC: addr:0x3240000 --length:0x080000
LOGO: addr:0x32C0000 --length:0x300000
EXPDB: addr:0x35C0000 --length:0xA00000
ANDROID: addr:0x3FC0000 --length:0x28A00000
CACHE: addr:0x2C9C0000 --length:0x17800000
USRDATA: addr:0x441C0000 --length:0x52C00000
FAT: addr:0x96DC0000 --length:0x54340000
BMTPOOL: addr:0xFFFF00A8 --length:0x000000
Format addr:0x481C0000 --Format length:0x4EC00000
>>Read phone information success.
these are the info , so please can some one help me urgently thankyou.
bcnboy
Good PM.
i have an MT6592M device with Android 5.1 kernel 3.10.72. im having problems making a full backup or dump of my rom. i have created readback from sp flash tools but its not creating preloader.bin. i makes the other necessary files when processed in mtkdroidtools > "to process the file ROM_ from spflashtool" option but there is no preloader.bin. the files seems to work fine since i tried it couple of times reflashing to my device. i tried to root my phone, checked that its been properly rooted, installed busybox and use mtkdroidtool's backup function and it fails at making preloader_and_dsp and wont backup the partitions aside from /system and /nvram, error msg says : "ERROR : Zero file, no space left on device!" and looking for answers there seems to be no method that worked in my case.
so i use readback to manually dump the preloader.bin address and using hex editor to view, it doesn't seem right since the header is wrong and its starting with EMMC_BOOT. i don't think i can reflash this preloader.bin file in case i will have issue with my device, right?
so, i need help if there are other ways to backup mediatek roms, or dump only the preloader.bin and make it flashable with spflashtools or anyone who can clean-up the dump i made and make it right for flashing back.
thanks.
here's the partition info as reported by mtkdroidtools and attached is scatterfile:
23/01/16 10:48:29 Part_Name Size StartAddr Type MapTo Region
23/01/16 10:48:29 preloader 0x0000000000040000 0x0000000000000000 2 /dev/misc-sd BOOT_1
23/01/16 10:48:29 mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1 USER
23/01/16 10:48:29 pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2 USER
23/01/16 10:48:29 protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3 USER
23/01/16 10:48:29 seccfg 0x0000000000040000 0x0000000001d00000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 uboot 0x0000000000060000 0x0000000001d40000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 bootimg 0x0000000000a00000 0x0000000001da0000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 recovery 0x0000000000a00000 0x00000000027a0000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 sec_ro 0x0000000000600000 0x00000000031a0000 2 /dev/block/mmcblk0p4 USER
23/01/16 10:48:29 misc 0x0000000000080000 0x00000000037a0000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 logo 0x0000000000800000 0x0000000003820000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 ebr2 0x0000000000080000 0x0000000004020000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 frp 0x0000000000100000 0x00000000040a0000 2 /dev/block/mmcblk0p5 USER
23/01/16 10:48:29 expdb 0x0000000000e60000 0x00000000041a0000 2 /dev/block/mmcblk0 USER
23/01/16 10:48:29 android 0x0000000060000000 0x0000000005000000 2 /dev/block/mmcblk0p6 USER
23/01/16 10:48:29 cache 0x000000001a800000 0x0000000065000000 2 /dev/block/mmcblk0p7 USER
23/01/16 10:48:29 usrdata 0x0000000151300000 0x000000007f800000 2 /dev/block/mmcblk0p8 USER
23/01/16 10:48:29 bmtpool 0x0000000001500000 0x00000000ffff00a8 2 /dev/block/mmcblk0 USER
Click to expand...
Click to collapse
wertzPH said:
Good PM.
i have an MT6592M device with Android 5.1 kernel 3.10.72. im having problems making a full backup or dump of my rom. i have created readback from sp flash tools but its not creating preloader.bin. i makes the other necessary files when processed in mtkdroidtools > "to process the file ROM_ from spflashtool" option but there is no preloader.bin. the files seems to work fine since i tried it couple of times reflashing to my device. i tried to root my phone, checked that its been properly rooted, installed busybox and use mtkdroidtool's backup function and it fails at making preloader_and_dsp and wont backup the partitions aside from /system and /nvram, error msg says : "ERROR : Zero file, no space left on device!" and looking for answers there seems to be no method that worked in my case.
so i use readback to manually dump the preloader.bin address and using hex editor to view, it doesn't seem right since the header is wrong and its starting with EMMC_BOOT. i don't think i can reflash this preloader.bin file in case i will have issue with my device, right?
so, i need help if there are other ways to backup mediatek roms, or dump only the preloader.bin and make it flashable with spflashtools or anyone who can clean-up the dump i made and make it right for flashing back.
thanks.
here's the partition info as reported by mtkdroidtools and attached is scatterfile:
Click to expand...
Click to collapse
HI I have the same problem with MT6592 1.7Ghz, unable to retrieve preloader.bin
Hope someone have answer for this.
kum512 said:
HI I have the same problem with MT6592 1.7Ghz, unable to retrieve preloader.bin
Hope someone have answer for this.
Click to expand...
Click to collapse
i already have solved this, but using manual method which means manually running readback on preloader.bin's actual address and region then again manually edit the resulting file for it to be flashable in spflashtools(u cannot directly use it)
wertzPH said:
i already have solved this, but using manual method which means manually running readback on preloader.bin's actual address and region then again manually edit the resulting file for it to be flashable in spflashtools(u cannot directly use it)
Click to expand...
Click to collapse
How to prepare the obtained file(backup) for SP Flashtool?
wertzPH said:
i already have solved this, but using manual method which means manually running readback on preloader.bin's actual address and region then again manually edit the resulting file for it to be flashable in spflashtools(u cannot directly use it)
Click to expand...
Click to collapse
Please wertzPH can you tell us how to process manually preloader.bin to be flasheable in SPFlash Tools? I have the same Issue with a mtk 81XX. I was made a full dump (including EMMC_User and EMMC_Boot1)
THANKS IN ADVANCE!
Martin
I need help to root my Aligator S5065 Duo phone. It ha Andoid 7.0 and the chipset is Mediatek MT6580.
Here is some info from the phone:
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : XXX
IMEI2 : XXX
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : 010901MT000000000000003891_155648
The idea was:
1) make a full backup using MTK Droid Tool
2) flash TWRP using SP Flash Tool
3) boot TWRP and install Magisk
Problems:
1) MTK Droid Tool v2.5.3. doesn't support this chipset and I didn't found a newer version - so no full backup
I've tried to download a stock ROM or a full backup.
I have found MT6580__ALIGATOR__ALIGATOR_S5065__alps-mp-n0.mp2-V1_droi6580.weg.n__Android_7.0.ispff but it seems to need Infinity CM2 Dongle for flashing, which I don't own.
I have also found ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.02_OS_1.1_20170927.zip which seems to be usable but not exactly the same as I have in my phone, at least it contains a scatter file. With the help of this scatter file I have I've read back my phone but the read imgs are considerably bigger, than the original ones in the zip - that doesn't seem right?
2) I have downloaded TWRP_3.2.3-0_20180803_UNOFFICIAL_MT6580_N.zip which should be a TWRP recovery for my chipset and the same kernel version, so I hoped it could work. But when trying to flash it with SP Flash Tool I get "PMT changed for the ROM" error message. The suggested solution for this error seem to be very risky (formating the phone, atc.), so I didn't dare to try ...
Now I'm stuck and I don't know how to proceed.
Any help would be really appreciated
Some progress:
I got a custom TWRP recovery image from Matty1993 <- thank you very much
I flashed it using adb and fastboot:
adb devices - successfully listed my device
adb reboot bootloader
fastboot flash recovery c:\adb\recovery.img - got this error message: "FAILED (remote: 'not allowedin locked state')"
Locked bootloader, unlocking ...
fastboot flashing unlock
- (bootloader) Start unlock flow
- OKAY [ 18.800s]
- Finished. Total time: 18.816s
Flashing the recovery.img
fastboot flash recovery c:\adb\recovery.img
Sending 'recovery' (10226 KB) OKAY [ 0.359s]
Writing 'recovery' OKAY [ 0.640s]
Finished. Total time: 1.030s
Success
fastboot reboot-bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.016s
fastboot erase cache (I don't know if it was a good idea but it was in the tutorial, I was following)
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.109s]
Finished. Total time: 0.125s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.016s
Now when booting the phone complains:
Orange state
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
In 5 second it starts to boot but it stays forever on the "POWERED BY android" logo
I can boot to TWRP recovery (also fastboot), so I did and flashed magisk (because the main goal was to root my phone) and selected to delete cache/dalvik.
I'm not able to switch off the phone, it reboots. I had tu pull the battery (luckily it's removable).
The phone info changed
BB Chip : mt6580
MS Board. : ALIGATORS5065
Build Time : Tue Jan 23 15:35:41 CST 2018
Krenel Ver. : 3.18.35+ ([email protected]) (gcc version 4.8 (GCC)) #2 SMP PREEMPT Tue Jan 23 16:11:14 CST 2018
Android Ver. : 7.0
SW Ver. : alps-mp-n0.mp2-V1-droi6580.weg.n
Custom Build Verno. : unknown
IMEI1 : unknown
IMEI2 : unknown
Modem Ver. ALIGATOR_S5065_OS_1.1_2018 0123
Bar code : unknown
The IMEIs and Bar code are now "uknown".
What did I wrong and what to do, to fix it?
forget MTK Droid Tool it is outdated and does not support scatter for devices > 4 GB. you can use SP Flash Tool for full ROM dump. First thing you should do is backup your nvram partition, hopefully it is not too late...
https://www.getdroidtips.com/backup-restore-imei-nvram-data-mediatek
If you already have backup of stock boot.img:
- copy file to /external_sd/TWRP/BACKUPS folder
- rename it to boot.emmc.win
- create a backup of current boot (just in case)
- restore renamed stock boot.emmc.win from TWRP
regarding boot stuck:
- Format Data and Wipe Cache from TWRP, reboot recovery, wipe again (Wipe -> Format Data -> type yes)
- reboot TWRP, check if /system /data and /cache is mounted/mountable (you should see folders or files inside)
- reboot system and wait 5 minutes, first boot may take a while because the data partition is forced encrypt
- if android is completely booted, check IMEI
Now, if your device is in good condition, reboot recovery and make a full TWRP backup.
Thank you very much for your help.
I did a dump before, using the SP Flash Tool and the scatter from the downloaded ALIGATOR S5065 – 7.0_MT6580_WL581M.LG.ALIG.HB.N.F.S12.B18.0927.V3.0 2_OS_1.1_20170927.zip file.
So I have a sort of a "backup"
Now I'm going to read and I'll report back how it went.
blakegriplingph said:
NVRAM data must have been wiped off somehow, as that's one reason as to why your serial numbers have gone kaput.
Click to expand...
Click to collapse
If this is the case, you can "download" (=flash) your backup files from SP Flash Tool. In scatter file change entries to "is_download: true". Open the edited scatter file with SP Flash Tool. Make sure you uncheck all checkboxes, except nvram, nvdata (and cache, if you still have problems with this partition). Double click on file name and select the file for each partition. Make sure EMMC_USER is selected. The file sizes must fit partition size. Do NEVER flash PRELOADER! Press start, then connect phone, then insert battery.
nvram.bin 5120 KiB (0x00500000)
nvdata.bin 32768 KiB (0x02000000)
cache.img 409600 KiB (0x19000000)
If done, hold Volume Up key while unplug + plug in USB cable, this will boot into recovery. Wipe Cache and Data
My sizes of the backup files:
nvram.bin 5 242 880 seems OK
nvdata.bin 33 554 432 seems OK
cache.img 419 430 400 bigger
Is there a way I can check the integrity of them before flashing?
And what when I get the "PMT changed for the ROM" error message?
I've attached the used scatter file
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Matty1993 said:
All good mate yeah orange state is because you unlocked bootloader and didnt factory reset [...]
If you still get dramas with orange state let me know ill manually patch the dm-verity out of your boot.img for you
Click to expand...
Click to collapse
Orange state just mean unlocked bootloader, you can't get rid of. Do not lock the bootloader again, just leave it orange state is fine...
I thought so and it doesn't really bother me
Matty1993 said:
Your device comes with out of the box encryption in your boot.img fstab your system path will be /dev/block/platform/mtk-msdc/******/msdc/by-name/system /system ext4 ro wait, "verify"
Click to expand...
Click to collapse
Zdendav said:
I did all the steps:
- wipe, format
- factory reset
hangs on the "POWERED BY android" logo, when trying to boot
- flashed boot.img in fastboot
- reboot
I was not fast enough to go onto TWRP, it tried to boot, hangs on the "POWERED BY android" logo
-reboot into TWRP
- wipe, format
- factory reset
still hangs on the "POWERED BY android" logo, when trying to boot
I can borrow exactly the same phone from a relative (fully working) - maybe I should do a full backup of it, then I'll have "clean" images of boot, recovery etc.
Meanwhile I did another full backup and this time I used WwR MTK v2.30 to create a correct scatter.
I attach both scatter files.
Click to expand...
Click to collapse
as @Matty1993 already figured out, your phone seems fine, just dm-verity prevents to boot because of recovery checksum mismatch. You have to disable dm-verity.
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
aIecxs said:
Should be fine if you use same scatter file used for read back. If you got "PMT changed" (probably wrong scatter file), you must restore all partitions (except preloader) with the exactly same scatter file you have created your backup. Then your phone should be restored to its original state no matter if scatter file was wrong. Once you get your phone in good condition, you can create your own scatter file with current partition layout from WwR MTK v2.30
Click to expand...
Click to collapse
I did try and I got the "PMT changed" even when I selected all partitons except preloader ..
I did borrow exactly the same phone from a relative and created a full backup and from it a proper scatter file. I compared both scatter files and there are differences (as expected)
I attach both scatter files
I don't know how to proceed.
1) Lock the bootloader?
2) Flash parts from the borrowed phone? Which parts?
PS I have also a backup of userdata taken in factory mode.
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
aIecxs said:
Install Disable_Dm-Verity_ForceEncrypt.zip from TWRP. This will patch your boot.img and modify fstab entries. Format Data, then use "Copy Log" option and upload recovery.log here
Click to expand...
Click to collapse
Done. Did it all in one go (without any reboot), then powered off.
Log is attached
aIecxs said:
don't flash anything with SP flash tool, just see my previous post. boot + recovery + nvram are identical, but tee1 + tee2 + teeinfo missing, and metadata + userdata have different size. keep the backup created with scatter file from WwR_MTK this seems to be the right one
Click to expand...
Click to collapse
Sorry I missed your post until I posted mine ...
I'll keep all backups until it's sorted out.
And thank you very much aIecxs and Matty1993 for all your help
thanks for the log. seems there is something wrong, maybe with TWRP or maybe with phone.
Code:
E:Primary block device '/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata' for mount point '/data' is not present!
Failed to mount '/cache' (Invalid argument)
Error installing zip file '/external_sd/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip'
Flash stock boot.img and stock recovery.img from fastboot. reboot into stock recovery. Wipe Data + Cache. reboot to bootloader. boot into TWRP from fastboot. copy log to sdcard and upload again. reboot your phone and wait 5 minutes.
I flashed the stock recovery and boot in fastboot in one go.
Then rebooted to recovery but there is only "Supported API: 3" in the lower left corner of the display and that's all.
What to do next?
Edit: It's even worse, I'm not able to enter fastboot, recovery etc., the phone doesn't react to the volume button and always show the orange message a boot to the Supported API: 3 screen.
This indicates something is wrong with cache partition. Usually a normal system boot from stock boot.img will fix this. If you can't enter fastboot mode, flash recovery from SP Flash Tool. Try this version it has changed fstab. This should fix the /data mount. Then you should be able to enter fastboot again.
Code:
[strike]/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata[/strike]
/data ext4 /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/userdata flags=encryptable=/dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/metadata
Regarding /cache try following from fastboot:
Code:
fastboot format:ext4 cache
after this wipe cache again from stock recovery (you can boot stock recovery from fastboot without flashing it). if cache still not mounted in TWRP, your only choice left is flash backup of cache partition from your friends phone from SP Flash Tool
edit: attachment deleted
Flashed your recovery, now it always boots into twrp, volume buttons still seem to not work, I'm still not able to enter fastboot.
Edit: I was able to enter fastboot by "adb reboot bootloader" when in TWRP, strangely "adb reboot fastboot" booted into TWRP.
I formatted the cache, rebooted into stock recovery, formatted the cache again.
Rebooted into TWRP, in file manager the cache is empty, in the mount menu I'm not able to tick any of the listed partitions to mount it ...
I'm not able to post the new log, it copies it to /data/media but in the file manager the location is empty ...
i have added some mount points, please download and flash again. you can copy recovery.log from adb
Code:
adb pull /tmp/recovery.log C:\adb\recovery.log
please post output of df and mount
Code:
adb shell
mount
busybox df -aT
/ # mount
rootfs on / type rootfs (rw,seclabel)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/ # busybox df -aT
Filesystem Type 1K-blocks Used Available Use% Mounted on
tmpfs tmpfs 463204 44 463160 0% /dev
devpts devpts 0 0 0 0% /dev/pts
proc proc 0 0 0 0% /proc
sysfs sysfs 0 0 0 0% /sys
selinuxfs selinuxfs 0 0 0 0% /sys/fs/selinux
tmpfs tmpfs 463204 32 463172 0% /tmp
adb functionfs 0 0 0 0% /dev/usb-ffs/adb