I murdered my 4007x. Please advise if possible.

[pmassie]

Hello
Thank you very much for all the info in these threads!
I was trying to follow the 'How to trick OTU Updater...' thread, and think I might have accidentally formatted the entire flash, without excluding the boot loader.
Everything was going fine up until after the format.
Immediately thereafter,

- windows would no longer detect the phone, with or without a battery
- phone wont start at all, recovery or otherwise

Following what I could find, Ive tried
- reinstalling drivers (from the OT upgrade tool)
- using a different computer
- using different versions of SP Flash (although because windows wont see the phone I doubt that would make a difference)
- OTU Updater cant see the handset either
- different cables (when connected the little blue LED on the phone lights up)

I don't have any way to recharge the battery other than the phone, but have no reason to think it is/was low (4.1V according to my multimeter).
I do have a full backup from MTK Tools, but cant restore because of the lack of connection.
I saw mention of a force flash mode, but when I hold vol+ and power up, nothing happens.

Does it follow that a bootloader format would cause these symptoms?
Is there a solution other than taking it to the agents?

Thank you for your time
Kind regards

[Brka]

Try that "forced download mode" - volume up + power on for 5-10 seconds,
(or just hold volume up) and insert usb cable, should appear as MTK USB VCOM port,
and just do full flash after - I already posted links, search for it.

problem might be, that you also erased NVRAM partition, so IMEI will be gone.

but, that's another part of this story.

b.r.
Alex

[pmassie]

Hi
Thanks for the response. I tried what you suggested (holding vol+ and power for 10 sec then plugging in USB while still holding buttons) but nothing...
If I managed to remove NVRAM, is that the end of the story do you think?
I checked my backup and it contains a userdata_nvram_only img file! Maybe I got lucky?
thanks again
Phil

[Brka]

Originally Posted by pmassie

Hi
Thanks for the response. I tried what you suggested (holding vol+ and power for 10 sec then plugging in USB while still holding buttons) but nothing...
If I managed to remove NVRAM, is that the end of the story do you think?
I checked my backup and it contains a userdata_nvram_only img file! Maybe I got lucky?
thanks again
Phil

Yes, you are lucky ....

Now, check attached picture, there is testpoint,
connect it to ground, and plug usb cable, it should be recognized via SPFT,
flash it, and later restore NVRAM, phone should be working.
(it just needs preloader.bin and DSP_BL, later can be detected in normal mode via SPFT)

also ... you should recharge battery on some external power source,
to be able to reflash it, as I remember.
(3.65-3.7v should be okay).

b,r,
Alex

[pmassie]

Thank you. This technique worked very well!
Phone is alive once more, but wont boot past operator logo... Any suggestions welcome, but will keep looking around.
Thanks again
Phil

[Brka]

Originally Posted by pmassie

Thank you. This technique worked very well!
Phone is alive once more, but wont boot past operator logo... Any suggestions welcome, but will keep looking around.
Thanks again
Phil

Check if you selected ALL files in SPFT (load scatter, and tick all unticked files),
select them manually.

Second, you may try to flash CWM / TWRP Recovery,
and after flashing, enter into it, and do all needed hard-reset / format operations,
that helps sometimes.

if not ... use pro_info file from sticky thread, edit PID,
flash into phone, and use OTU updater, it will restore phone fully.

b.r.
Alex

[pmassie]

Thanks!
Tried the pro-info sticky technique,
- changing the 3 chars from S16 to A11 (in both places, and just the first)
- Formatting (not bootloader and NVRAM this time )
- Flashing new pro-info
didn't trick the updater - no new version avail message. i missing something, not sure what though.

Tried flashing with my backup as well as with the rom that you posted as well - same result. I also tried flashing the nvram . bin from my MTK backup folder - no change.

will try CWM/TWRP recovery, as soon as I google it

Thanks again. That earthing trick was pretty amazing!
regards
Phil

[Brka]

Originally Posted by pmassie

Thanks!
Tried the pro-info sticky technique,
- changing the 3 chars from S16 to A11 (in both places, and just the first)
- Formatting (not bootloader and NVRAM this time )
- Flashing new pro-info
didn't trick the updater - no new version avail message. i missing something, not sure what though.

Tried flashing with my backup as well as with the rom that you posted as well - same result. I also tried flashing the nvram . bin from my MTK backup folder - no change.

will try CWM/TWRP recovery, as soon as I google it

Thanks again. That earthing trick was pretty amazing!
regards
Phil

That thread needs some updating ...

Anyway, just change PID, don't change those other chars.
You must put some unbranded pid
(Telenor, T-Mobile, Vodafone and other pid's cant be updated)

here are some PID's :

4007X-2AVDZA1 = Vodafone S.Africa
4007X-2AALZA1 = S.Africa - Should be unbranded and allow updating

there are just those 2 PID's for South Africa region (ZA).


After you change PID - flash into phone pro_info and retry with OTU updater.

b.r.
Alex

[pmassie]

Thanks again!

seems there's no hope for me & my phone.
Tried every combo of:
- formatting (no bl or nvram),
- restoring all or no files in the scatter file + pro_info,
- changing pro_info's PID to the unbranded one you suggested
- changing pro_info's 13th to 15th digits or not

Just cant seem to trick the updater... might try a European PID (England maybe?)

Also, it seems there is no CWM or TWRP recovery for this Alcatel... will keep looking though

Thanks for all your time. Would love to figure this out am learning quite a bit about the phone, but the wife is giving me grief (rightly so) about late nights...



**** EDIT: Merged post


Thank, will try.
May I ask, the nvram . bin that is generated by mtk tools backup... do i flash that the same way as the rest of the files (delete __NODL_ from scatter, and point SPFT at the nvram . bin file), downloading to 0x0300000, with a length of 002fff0? Im not sure if you might know this, but the reason I ask is the SPFT 3.x throws me an error when I try this technique, but 5.x seems to work fine...
Also, for the updater tricking, do I still need to format the phone first (except bootloader etc)?
Apologies for the questions and thanks! will try the other roms tomorrow, I only knew about the ZA one... maybe that's the problem...

thanks
Phil

[Brka]

Just to check - you tried all 3 flashes I uploaded ?

ROM1 - ROM2 - ROM3

SPFT - v3 HERE or V5 HERE

retry, and check if all files are selected before flash.

p.s. With any of these flashes, phone should power on,
but probably with imei corrupted, if you did full format.
(or, check if it made some backup, under SPFT folder "BackupData")

p.s.2 Important part is - that you have phone in state that OTU can see it
(and it needs pro_info partition, with "clean" PID, to allow updating)

p.s.3 Check THIS thread for pro_info files

p.s.4 It doesn't matter if phone power on as 4007D model (with 2 signal bars),
important is, that you return it back to some working condition,
from that part is much easier to fully fix it.

p.s.5 I am uploading some revival pack with full instructions, will post links later.


**** EDIT:
Full Recovery pack with instructions - download HERE
CWM and TWRP Recovery pack with instructions - download HERE

NVM Backup for MTK Droid Tools - attached to this post.
(unpack it to folder C:\MtkDroidTools_v253\BackupNVRAM ),
two files into that folder - one bin and one tar.

now ... time to try it all ... and post results.
If it worked, please write the procedure that worked for you.


**** EDIT:

Just to clarify all about addressing :
- Scatter file is "address map" file
- Beginning of some partition is written in scatter
- Length of that partition is up to beginning of next partition (next partition minus start of previous = length , in HEX)
- You can do the same thing with "Write memory" option, entering correct addresses

And to clarify regarding OTU updater :
- OTU needs phone that can normally boot (with preloader.bin or preloader.bin + DSP_BL)
- OTU needs pro_info file, because it reads PID from it, compare to server and download needed files
- All the rest partitions, are not necessary for OTU (so you can format all, if you want)
- Just edit PID in pro_info, nothing else, if fail, try with oter pro_info files (download all from forum)

You have some pro_info files in packs I uploaded, and one new attached.

pid's to put when editing, try some of these : (these are all existing pid's)
(first 3 are possible success)

4007X-2AALEU1
4007X-2AALFR1
4007X-2AALIT1
4007X-2EC6AO3
4007X-2ALWS1
4007X-2ARGFA3
4007X-2AALNA1
4007X-2AALME1
4007X-2AALKE1
4007X-2ARGMD3
4007X-2AVDZA1
4007X-2AALAP1
4007X-2AALMA3
4007X-2AALMA1
4007X-2ATZTN1
4007X-2AALDZ1
4007X-2AVVBG1
4007X-2AATTE1
4007X-2ARGMA3
4007X-2AM9MZ1
4007X-2ARGTE5
4007X-2ARGTE3

b.r.
Alex

[pmassie]

thank you so much for all this time and effort.
I'm only getting to this now, but it looks more or less promising. I followed your revival instructions, and the only thing really different to what I was doing before is that I'm now using the pro_info from your revival pack (4007d vs 4007x).

Different pid, but otu is finally tricked! My suspicion is that the pids I was using before, both the vodaphone and 'clean' ZA one weren't that clean after all. Anyway otu is actually downloading something now, which is AMAZING .
I'll report back with methods and results shortly...
thanks again

[Brka]

In short ... it will work.

One and only real problem with pro_info is, that not all PID's can be updated.
(so far in my investigation - branded firmwares can not be updated, but some rare can)

keep playing, and of course, post your results,
or some easy revival manual/method, so it can help others.

b.r.
Alex

[pmassie]

Ok, so here goes. Succesfully revived my phone thanks to bRkA.
Using instructions, SPFT 5.1343.01 and 'Backup and ROM - for SPFT' from bRkA's revival pack

- Phone unplugged, battery removed
- Run SPFT
- Download tab - load MT6575_clean_scatter . txt.
- Format tab - checked validation, auto format flash and Format whole flash except bootloader, click start
- plugged batteryless handset
- format complete - remove handset from pc

- Download tab - load MT6575_scatter__Preloader . txt
- Make sure PRELOADER & DSP_BL are checked
- Click download
- plug in phone
- earth the pin referenced above post - hold until files are flashed
- remove phone, and disconnect earth

- Download tab - Load MT6575_scatter_ . txt
- only check PRO_INFO. In the 'location' column click the blank cell and browse to nodl_pro_info (same ROM) file
- click download, attach batteryless phone (no earth required) and allow to flash

- If battery is empty, may need to flash whole ROM and charge (not sure which sectors handle this). At this point phone wouldn't boot past logo, but did charge.
- With full battery (download was extremely slow) run One Touch mobile upgrade and allow to upgrade your phone

- After update is complete, you should now have a working, booting 4007d in a 4007x phone, but with Russian(?) language pack
- can change the language easily in first few screens.
- I tried many of the 4000x- PID's (but not all!) and none would trick the updater.

I checked the phone status and my IMEI seems to be in order. (theres only 1 right?)
Now to figure out if I can set the phone back to a single sim version, with english default.

I tried flashing the full rom t-4007x-2AVDZA1_by_bRkA and changed pro_info to appropriate pid but phone reverted to logo screen hang
will try and figure out which files I need to flash...
Thanks again, great to have the phone operational again!

[pmassie]

Thanks for everything! Definitely learned a LOT!
I tried every pid in the list this afternoon and none of them fooled the updater

I guess the pid which would suit me the best would be
4007X-2AALEU1 - Is this an unbranded European Union rom?

No hurry though... got an insane fortnight coming up.
The phone actually seems a little more responsive now (4007d) than it used to with the vodaphone za version!
Cheers
Phil

[Brka]

Get your ROM file - HERE

Maybe you will need to do same "revival" procedure,
to write preloader + DSP_BL + boot + uboot, then flash formware normally.

and when full flashing, select custpack file manually.

after flashing, do hard reset from recovery.


b.r.
Alex