Related
I'm having an irritating problem.
I've rooted my wife's Gen 1 Orange SF with Androot, even repeated it when I started having problems to make sure the root had worked. SuperUser is installed and working so I know it has gone OK.
I've installed Recovery Manager v0.36, which has root access.
The current recovery is listed as "unrecognised"
I flashed the following CWM - recovery-clockwork-3.1.0.1-blade-gen1.img (MD5 checksum correct)
I get an "installing" message, then back to the Recovery screen and the recovery is still listed as "unrecognised".
One of the guides I found on Modaco is quite specific about using Recovery Manager v0.34 (though I suspect it just hasn't been updated with the latest release) so I've also tried this using that version and no joy.
So... I thought I'd try the FASTBOOT method. I turn the phone off, remove and replace the battery. Turn the phone on whilst holding the up volume button, and the phone just boots up normally. I've tried this repeatedly, I don't get the big grey square that people report when FASTBOOT fails, I just get no response at all.
Grrrrr!
Any thoughts?
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
I also had the same while trying to flash a recovery to my friend's Blade. I understood that i have been flashing the wrong recovery all this time (though it showed for gen1 and i had a gen1). I used the given recovery(link provided below), and it worked for me like a charm. Use the link download on root of sd card. Use recovery manager to install it. If the recovery manager shows that it has identified the cwmod version then its done or else if it again says unrecognised try different versions of cwmod.
Preferably after getting cwmod to working convert your gen1 to gen2 (wbaw method). Then you can flash a custom rom and use ROM manager to upgrade your cwmod recovery.
http://android.podtwo.com/recovery/archived/recovery-clockwork-3.0.2.8-v9-gen1.img
To Convert gen1 to gen2:
http://forum.xda-developers.com/showthread.php?t=1103096
harmohn said:
Hmm, when you power up holding volume up key (held for a couple of seconds) does you phone show a static green android logo, or does it boot up fully to the lockscreen?
If only to the android logo, means you're in fastboot.
Edit: you can replace the green android logo with Orange's logo in the above comment if you haven't flashed an alternate ROM on the phone as yet.
Click to expand...
Click to collapse
He hasnt been able to install CWmod yet so no green logo will appear. Due to unrecognised version only DELL logo appears and hangs or it reboots normally. And yes FASTBOOT is not enabled in gen1 devices so thats why i say to convert to gen2 as soon as possible.
Hi Be4con,
I flashed a batch of 10 blades the other day, and wrote my own little guide for it. I had exactly the same problem as you with the first two i tried to flash.
The guide on modaco does work, but i found i had to use a much older version of clockwork mod. I used 2.5.0.8 (if i remember correctly) not at work just now so cant see my notes. This was picked up by the recovery no problems and i was able to move on from there.
Hope that helps
Hi
You have try to flash directly to your device with a terminal emulator
type SU
accept SuperUser autorisation
type flash_image recovery /sdcard/recovery_xx_xx.img (you find the good version on the recovery on internet)
reboot your phone with volume + down
if you have any problem to find the fine recovery or to flash the recovery contact me on pv . this method work with my zte gen1
Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Now does ur mobile boot ? Or is it stuck in the logo ?
Hakuna matata !
Sanjuujosephh said:
Now does ur mobile boot ? Or is it stuck in the logo ?
Hakuna matata !
Click to expand...
Click to collapse
Well I already stated (if you read my whole thread) that it works normally, running 4.4.2 atm without microSD card inserted, it works like the past except for two points:
1- My root access is gone.
2- I can't reboot into recovery mode at all, no matter what I try.
Wow u screwed up ur recovery itself ....wow u r awesome ! Just check if it goes to download mode if it does then flash it again with the latest firmware .... After flashing immediately try going to recovery and if u do ..... do the reset and wipe cache
Hakuna matata !
Sanjuujosephh said:
Wow u screwed up ur recovery itself ....wow u r awesome ! Just check if it goes to download mode if it does then flash it again with the latest firmware .... After flashing immediately try going to recovery and if u do ..... do the reset and wipe cache
Hakuna matata !
Click to expand...
Click to collapse
After I flash the firmware it automatically goes to a recovery screen, a progress bar gets filled then opens the Android system normally. After that when I try to go to recovery mode again it goes back to download mode again with the error text "Could not do normal boot".
Problem.... Fixed? .___.
Well for some reason on the third (and thought it's hopeless) attempt to flash the firmware again, I managed to open recovery mode after it, I was kissing the Reset Factory button.
As long as I find this weird, working on many attemps (maybe Samsung software itself fails?) I find this thread useless, thanks given to Sanjuujosephh! I inserted my microSD and it's working now, rebooted again into recovery and it's working as it should be.
citBabY said:
Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Click to expand...
Click to collapse
Dear friend,
Try my rooting thread at http://forum.xda-developers.com/gal...ps/galaxy-s5-mod-apps-kitkat-grand-2-t2821638
This is made specifically for the KitKat Grand 2.
The message "Could not do normal boot" came as a result of using 4.3 recovery on 4.4.2.
Do not ever attempt to revert to 4.3 as this will HARD BRICK YOUR PHONE'S MOTHERBOARD.
---------- Post added at 06:49 PM ---------- Previous post was at 06:46 PM ----------
citBabY said:
Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Click to expand...
Click to collapse
Dear friend,
Try my rooting thread at http://forum.xda-developers.com/gal...ps/galaxy-s5-mod-apps-kitkat-grand-2-t2821638
This is made specifically for the KitKat Grand 2.
The message "Could not do normal boot" came as a result of using 4.3 recovery on 4.4.2.
Do not ever attempt to revert to 4.3 as this will HARD BRICK YOUR PHONE'S MOTHERBOARD.
اقرأ الموضوع اللي كتبته خصوصي للجراند 2 بنظام كت كات
رسالة Could not do normal boot طلعت بسبب استخدام ريكفري قديم ع الكت كات
الموضوع الجديد فيه ريكفري جديد.
Help me plzz
hey.... wht did u do evn i m stuck there??? plzzz help..got KitKat on my Grand 2 got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot"
citBabY said:
Well I already stated (if you read my whole thread) that it works normally, running 4.4.2 atm without microSD card inserted, it works like the past except for two points:
1- My root access is gone.
2- I can't reboot into recovery mode at all, no matter what I try.
Click to expand...
Click to collapse
i think you should reset your phone
and if it doesn't work then try another country's rom
thankyou
hey bro, I have problem same to u..
Bro...I have same problem..?? I cant go to recovery mode showing Could not boot normally...etc..This happened after I tried CWM using Odin ..I always go download mood and...when i pressed factory reset button ..it didnt rest and go download mode again...plz help me bro...thanks
As long as I find this weird, working on many attemps (maybe Samsung software itself fails?) I find this thread useless, thanks given to Sanjuujosephh! I inserted my microSD and it's working now, rebooted again into recovery and it's working as it should be.[/QUOTE]
Bro, please don't use king root or any other root.
Solution
Please download the stock firmware and then go to download mode flash the stock firmware and root your phone again. Then recovery mode will work.
Thank you
Sorry for errors.
Sent from my SM-G900H using XDA-Developers mobile app
I'm a newbie but I fixed mine...
I've had this happen and it is frustrating to say the least. But I fixed it though. This is what I did: CAVEAT: Please read up all the FAQs, search the right firmware for your phone and the appropriate versions, KitKat vs Jelly Bean, etc. otherwise if your phone is bricked...don't blame me.
I have a 2nd-hand Galaxy Grand 2 and so warranty issues are a non-issue for me. All the files I've found were downloaded on this forum. I flashed ROM with my PC with Odin program installed.
I used Odin3 (v.3.07). (To install Odin program search the this forum). I also reflashed the recovery TWRP file "twrp_ms013g-build2.tar" Including the firmware G7102 Stock. My file was: G7102DDUBOB1_G7102ODDBOB1_G7102DDUBNK1_HOME.tar.md5. (Search for it.) Oh, you may want this file: CF-Auto-Root-ms013g-ms013gxx-smg7102.tar.md5 which may help with rooting your phone if you haven't already done so.
I did the Recovery 3-button Samsung phone groping procedure (you know what I'm talking about Volume Up/Down button + power + home button)... but to no avail...I keep getting that boot loop (Unable to normal boot...etc). You know that stupid "Downloading" Android logo (with the blue worded script on the top left-hand corner) with message ..."Downloading ...Do not unplug source..." Well, I plugged the USB cable to the phone to my computer and Odin program recognized it (it'll read "Added"). The phone didn't give any indications that it was doing anything. Btw, if your Odin program doesn't recognize your device then you should find out why it doesn't. If it recognized it before and you flashed with the Odin program before, I don't see why it won't recognize it now? Some say it's the USB cable but I can't logically accept that kind of superstitious BS. Come on, it's a copper/aluminum wire cable wrapped in pvc -- not a script. A cable is a cable is a cable. If it worked before, it'll work again unless it's cut inside the pvc tubing. You can use a digital multimeter to easily test that for continuity (albeit with really tiny leads to be able to connect to the mini USB side). Anyways, if your Odin program won't recognize your phone, maybe try using a lower version, or re-installing, or another similar type of program that will work. I'm assuming you did install the Samsung USB driver for your PC (e.g. mine is -v1.5.61.0 -search for your appropriate version) so that your computer will recognize your phone when cable is hooked up.
DON'T FORGET TO have the "Auto Reboot" and "F. Reset Time" boxes checked on the Odin program. Then select PAD button and browse for your TWRP file (above) and hit "Start." The Odin will flash it and you'll see a light blue bar under the Android logo (on your phone) that will go from left to right and when finished....whooooohooo the phone auto restarts back to your last OS state without losing any info on the phone. At least it worked for me. Hope that helps. Sorry for the long post.
hi i am in official android 4.3 on my g7102 and i wanna install a recovery file. but every recovery file i tested dosnt work on android 4.3. can you help me?
If u have knox bootloader do not try to downgrade just get kitkat one and in odin check phone bootloader update
Seems like u really guys screwed up the recovery. Somehow on my first try of flashing a zip file (recovery), i got stuck on download mode and wont boot normally. When I fixed the problem, the phone boots normally but the recovery is the only problem I got. I fixed this problem for about 10 days ago, all i did was to reflash the recovery again, orrr flash other version of the recovery (if the downloaded recovery version didnt work) or flash other recovery if the another recovery didnt work. Make sure the recovery is working on the version of you're phone (jelly, kk, lollipop, marshmallow or nougat) and working also on the model version.
I know this is an old thread but I hope this reply helped
hello guys.
first i will start with the beginning. i have a grand 2 duos g7102 phone. i rooted the phone and installed CWM recovery in order to flash custom rom CM 12.1 Lollipop 5.1.1 everything was running well until i upgraded to CM 14 Nougat 7.0 COSMO, i didn't like it and when i wanted to get in recovery mode again it stopped working. Now i can't boot in recovery mode at all. Not showing CWM recovery like before only recovery booting for few second and after that the dead android and No command and there is more writing down the screen like Supported API: 3 but it is hard to read because the screen is always flashing.
i someone faced this problem before please help !!!
thanks in advance
Guys guys i had the same problem with my grand 2 7102.
I rooted my phone and flashed a recovery via odin.
But as i press the button combos it says. Could not do normal boot.
So, i found a solution for it.
Downloaded flashify for play store.
Extracted img. File of twrp recovery provided in the grand 2 thread 😬,
Flashed it with flashify
And guess what i was in the recovery and after that no problem came with the recovery flashing 🙂
If you guys keep having problems with no-pc flashing, try the pc flashing cause this is the better way of flashing other than apps.
I had the could not do normal boot problem
Do this ...
Google cwm test 4.4 ms013g.tar and download it
Put it in PA or PDA uncheck autoreboot keep freset time checked
Flash the file then when you get pass message in odin , remove battery and reinsert it and go to recovery mode directly with vol up + power button.
NOTE : Don't try to normal boot to system
Any expert who can HELP!!!
i have an asus a500KL zenfone 5 tried software update after reboot got ERROR: invalid boot image
i am fairly experienced with root access, custom roms however this device was never rooted and have been trying to fix this issue for a few days.
I am able to get to csc mode, also powering off and entering BLUE SCREEN csc mode holding power ands vol up for 3 cycles until the screen goes blue, even installed different drivers and full restart of pc and phone, still not work.
I have tried ALL the flash asus tools and everything. tried a few intels but they dont even begin to work as mine is an ARM.
fastboot recognises csc mode!!!
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
I have tried every key combination under the sun. (Timing, P + (+), P + (-), P + (+ & -), in all combos and timing combos.
Power + Vol Down gets me to the SD Update option.
CLick the top to continue and the bottom to reboot.
I have tried both and they both take me to the ERROR: invalid boot image
im stumped.
Ive Messed with HTC, Samsungs, Sony, Huawei for gods sake, even iphones and have never come across an issue like this that is so impossible to fix. I think i may have hit my first brick.
Any help will be greatly appreciated.
Regards
I have the same problem...
I have tried everything and I am still stuck with csc mode.
Please help
Best!
jaza-g said:
Any expert who can HELP!!!
i have an asus a500KL zenfone 5 tried software update after reboot got ERROR: invalid boot image
i am fairly experienced with root access, custom roms however this device was never rooted and have been trying to fix this issue for a few days.
I am able to get to csc mode, also powering off and entering BLUE SCREEN csc mode holding power ands vol up for 3 cycles until the screen goes blue, even installed different drivers and full restart of pc and phone, still not work.
I have tried ALL the flash asus tools and everything. tried a few intels but they dont even begin to work as mine is an ARM.
fastboot recognises csc mode!!!
I can flash a boot.img but that is it, does not change the situation.
Everything else gets an error, something like ERROR: Security prevents this action or something about it being locked. I think it might mean the bootloader is locked and cant access anything pretty much.
I have tried every key combination under the sun. (Timing, P + (+), P + (-), P + (+ & -), in all combos and timing combos.
Power + Vol Down gets me to the SD Update option.
CLick the top to continue and the bottom to reboot.
I have tried both and they both take me to the ERROR: invalid boot image
im stumped.
Ive Messed with HTC, Samsungs, Sony, Huawei for gods sake, even iphones and have never come across an issue like this that is so impossible to fix. I think i may have hit my first brick.
Any help will be greatly appreciated.
Regards
Click to expand...
Click to collapse
Do you happen to be QDLOAD mode or QHSUSB? My experience working with SD400 devices, you need to nuke one of your partition to be able entering QDLOAD mode.
edit : For some reason I believe the CSC mode you got into is actually fastboot mode. Did you tried running any fastboot command? If fastboot cant detect, manually replace csc driver in device manager with fastboot driver.
Can you provide a picture of the error codes ?
http://imgur.com/QQ7OxDZ
like this i believe?Im having the same problem
Hi All,
If you have CSC MODE and ERROR: INVALID BOOT IMAGE
I found a solution, that is worked for me.
You don't have to turn on the USB debugging on your phone, connect to the PC, etc.
Steps:
1. Download recovery.img from Official Stock ROM (e.g. WW_12.4.5.58)
1.1. IMPORTANT: Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW
2. Download Official Firmware from asus.com/Phone/ZenFone_5_A500KL/HelpDesk_Download/ (e.g. UL-ASUS_T00P-WW-12.4.5.58-user.zip)
2.1. Read the Description!!!
2.2. IMPORTANT: Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW
3. Copy the recovery.img and the <firmware>.zip files to the root of external SD card
4. Power off your device
5. Simultanously push the Power + Volume Down button and waiting for the choice screen
5.1. Choice screen:
1. Enter SD download mode
2. Exit update mode
6. Choose the "1. Enter SD download mode"
7. Choose the "apply update from external storage"
8. Choose the the <firmware>.zip file (e.g. UL-ASUS_T00P-WW-12.4.5.58-user.zip)
9. Waiting for the installation finished
10. Choose the "reboot system now"
Best Regards,
R.
invalid boot image means doesn't go to boot loader, how can i update from sd card then ?
Steve Al-Mousa said:
invalid boot image means doesn't go to boot loader, how can i update from sd card then ?
Click to expand...
Click to collapse
boot doesnt mean bootloader...
thanks for the explaination, I'm not an expert in this, just having this problem since i upgraded the firmware by OTA rebooted and got stuck, I've tried all methods here but useless, i can go to csc only, i get invalid boot image when i go to sd download... any suggestions ?
thanks
Try this
https://forum.xda-developers.com/zenfone-5/general/stock-a500kl-zenfone-5-lte-t3303475
Did you ever get this sorted? I have the same issue......
Steve Al-Mousa said:
thanks for the explaination, I'm not an expert in this, just having this problem since i upgraded the firmware by OTA rebooted and got stuck, I've tried all methods here but useless, i can go to csc only, i get invalid boot image when i go to sd download... any suggestions ?
thanks
Click to expand...
Click to collapse
Dagk66 said:
Did you ever get this sorted? I have the same issue......
Click to expand...
Click to collapse
I have been informed by the stupid Asus Thailand that the main board should be changed
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Renojjv said:
Hi,
I couldn't figure out where to ask this query since I couldn't find anything regarding my phone. I own a Lava_R1s with StarOS V3.3 with Android Version 6.0. This is a phone available specifically in the U.A.E market since its made without camera and GPS so that it can be used in the oil field.
I tried to root the phone and now its soft bricked. I can enter fastboot mode and recovery mode (TWRP) but every time i try to switch on the phone it keeps going into a loop of the "Lava Powered by android" and switches off and then continues to keep doing that.
Here is what i did.
1. I used fastboot to unlock the OEM.
2. Then I flashed TWRP as recovery for the mobile.
3. After that i installed SuperSU zip file.
After all these steps my phone refuses to start up. It just comes to the LAVA powered by android screen and stays on that screen till i press the power button.
Further more I tried flashing the boot and system with Stock ROM files downloaded from needrom.com. That hasn't helped. In fact the looping of the initial screen started after flashing boot and system files (I used img files for Lava R1 Lite since those where the only ones i could find).
Would be really grateful if anyone could provide me a solution for this issue.
Another thing is that a lot of my colleagues have the same phone, so if there is anyway to extract the rom from their phone and install on mine without actually rooting their device it would also work for me i guess.
Renojjv
Click to expand...
Click to collapse
Check my reply in this post
https://forum.xda-developers.com/android/help/softbricked-lava-r1s-please-help-t3730982
Hello, can somebody help me with a Lenovo A1000 ?
At first the phone did not boot, it was stuck at the boot logo so I thought it might be an easy fix , just to reflash the phone .
I managed to get into recovery mode and from what I remember , it was written in red color this text : " a1000_usr_s29798_1511241708_sprd7731_ro "
Then I read on the internet the procedure on how to flash the phone, installed all the drivers and the SPD upgrade tool version 4 and flashed the firmware : " Lenovo_A1000_S113_SPRD7731_20170525 " but after the flashing was done, the phone does not respond to anything anymore, it does not open , does not show anything if I plug in the charger, no recovery , no boot logo , nothing. It only "works" when trying to flash with SPD upgradetool if I hold the volume buttons pressed and insert the cable , then SPD flashes it again, and only with that specific firmware, I have tried multiple ones but they always fail, at repartitioning.
The phone is dual sim if that makes a difference, and on the back it only said A1000 , i dont see the "m" anywhere to indicate that it's a A1000m model.
I have tried to flash it over & over again, disabled the imei and nv options in the two gears in SPD , it flashes but no boot , no response from the phone after the flash is done, nothing.
I opened the phone to look inside if the connectors are all attatched, everything seems fine hardware wise.
If anybody knows anything on how to revive the phone, I would appreciate it & thank you in advance.