Related
Well, here is the story:
I had downloaded a SBF file for the DROID 2 not paying attention to the fact that it said A955 and after I had accidently flashed it I noticed it said "Do NOT flash for the DROID 2 GLOBAL" and I now have a paper weight that only boots into the DROID 2 bootloader. D2.37. it says Error: A5,70,00,00 MEM_MAP Blank Service req'd
Every time I try to flash a droid 2 global stock SBF it sais Critical Error FEBE 0047. I think the only way for me to unbrick my phone is to flash a SBF of the Droid 2 Global D0.11 Bootloader file, or any Droid 2 Global Bootloader file, since SBFs for The Droid 2 Global and the Droid 2 Global R2D2 both work on my phone, Would there be any way to fix my problem, or at least SBF-Flash a Bootloader into my phone, and if there is a lockup would there be a way to bypass the SBF error-s?
Update: Tried exSBF as Gasai Yuno said, this is my results:
On Screen: Waiting for phone: Connected
>>Uploading RDL03: 100.0x
--OK
>>Verifying Ramloader
-- OK
>> Executaing Ramloader
RX(7) : [02}ERR[1e]G[03]
!! Failed
>> Rebooting
and my phone still has the Critical Error FEBE 0047
Tried with a different SBF and this is my result:
Indexes 0-14 Unexpected Chip 32
Bunch of numbers from slots 0-14
Then:
Droid X found.
?? uploading RDL03
Uploading 100% OK
>>Verifying Ramloader
--OK
>> Executing Ramloader
Expected ACK
RX(9) [02]ERR[G[03]08
!! Failed
>> Rebooting
and still the FEBE 0047
sd_shadow said:
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
are you sure you have a D2G?, bootloader doesn't usually change if you flash wrong SBF, just says
Bootloader
D0.11
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Batery OK
OK to Program
Transfer Mode:
USB
Click to expand...
Click to collapse
I'll try that SBF, but I'm not sure if its a D2G boot loader, it used to be D0.11 but after flashing the Droid 2 SBF I see the 2.37 with that error, but let me try that sbf
jabberwockish said:
What version number was the D2 SBF file you flashed?
Have you tried any other D2G SBFs, or only the 2.4.29 one?
I am not certain, but I don't think any of the available D2G SBFs include a bootloader. When/if an SBF for 4.5.629 leaks, it should include the updated one.
Click to expand...
Click to collapse
I used the 2.4.29, the 2.4.33 and the 2.4.608 ones, but I'll try the one SD shadow mentioned
Update: Well, I had found a Full SBF file, and flashed it, somehow that got through my FEBE 0047 problem and my phone is flashing now...
Try ezSBF.
Gasai Yuno said:
Try ezSBF.
Click to expand...
Click to collapse
Tried that with the 1KDStaz_D2G_2.4.29 file,and more, and this is what I get:
On Screen: Waiting for phone: Connected
>>Uploading RDL03: 100.0x
--OK
>>Verifying Ramloader
-- OK
>> Executaing Ramloader
RX(7) : [02}ERR[1e]G[03]
!! Failed
>> Rebooting
and my phone still has the Critical Error FEBE 0047
Tried with a different SBF and this is my result:
Indexes 0-14 Unexpected Chip 32
Bunch of numbers from slots 0-14
Then:
Droid X found.
?? uploading RDL03
Uploading 100% OK
>>Verifying Ramloader
--OK
>> Executing Ramloader
Expected ACK
RX(9) [02]ERR[G[03]08
!! Failed
>> Rebooting
and still the FEBE 0047
What version number was the D2 SBF file you flashed?
Have you tried any other D2G SBFs, or only the 2.4.29 one?
I am not certain, but I don't think any of the available D2G SBFs include a bootloader. When/if an SBF for 4.5.629 leaks, it should include the updated one.
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
are you sure you have a D2G?, bootloader doesn't usually change if you flash wrong SBF, just says
Bootloader
D0.11
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Batery OK
OK to Program
Transfer Mode:
USB
sd_shadow said:
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
are you sure you have a D2G?, bootloader doesn't usually change if you flash wrong SBF, just says
Bootloader
D0.11
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Batery OK
OK to Program
Transfer Mode:
USB
Click to expand...
Click to collapse
I'll try that SBF, but I'm not sure if its a D2G boot loader, it used to be D0.11 but after flashing the Droid 2 SBF I see the 2.37 with that error, but let me try that sbf
jabberwockish said:
What version number was the D2 SBF file you flashed?
Have you tried any other D2G SBFs, or only the 2.4.29 one?
I am not certain, but I don't think any of the available D2G SBFs include a bootloader. When/if an SBF for 4.5.629 leaks, it should include the updated one.
Click to expand...
Click to collapse
I used the 2.4.29, the 2.4.33 and the 2.4.608 ones, but I'll try the one SD shadow mentioned
Update: Tried the SBF jump failed again. I really think I should flash a SBF of the bootloader, if there us a possible way there is a boot loader file, would there be a way for me to extract it from a SBF file?
Sent from my Glitched Icy Fassy using XDA
Attaching the bootloader image.
Thanks, I'll try it as soon as I reach my desktop
Update: Ok, that file did not work either, I think I'll try to edit a Droid 2 SBF and sneak the bootloader into there if it's possible :s )
Sent from my SCH-I500 using XDA
Gasai Yuno said:
Attaching the bootloader image.
Click to expand...
Click to collapse
I don't believe I have encountered this file before. Is it possible flashing this onto a D2G that has received the .629 update would enable downgrading to an older stock firmware (2.4.x or 4.5.60x) without bricking?
Edit: Never mind, I should have read this thread before posting that. Nice to know some more experienced folks had the same thought, though!
sd_shadow said:
the 4.5.629 SBF is out GB2.3.4/4.5.629 NS Device Full SBF
Click to expand...
Click to collapse
I'm not sure I believe that file is really compatible with retail D2Gs. Forgive my skepticism, but (1) the file name is in a completely different format than previous leaked SBFs, (2) the file name includes "4.5.1_57" rather than "4.5.629," and (3) that poster's grasp of English seems…tenuous (by which I mean no insult to him or her; only that it makes accurate understanding of their intended meaning more difficult).
jabberwockish, I'm afraid that 1FF-p3_droid2we_cdma_droid2we-user-2.3.4-4.5.1_57_D2GA-59-120117-test-keys-signed-Verizon-US.sbf is fully compatible with retail A956. Sorry to disappoint you.
I also regret to inform you that people have used this SBF image to produce the unbricker.
Please accept my condolences.
You have a wicked sense of humor, G.Y. Thanks for the information.
R2D2
Gasai Yuno said:
jabberwockish, I'm afraid that 1FF-p3_droid2we_cdma_droid2we-user-2.3.4-4.5.1_57_D2GA-59-120117-test-keys-signed-Verizon-US.sbf is fully compatible with retail A956. Sorry to disappoint you.
I also regret to inform you that people have used this SBF image to produce the unbricker.
Please accept my condolences.
Click to expand...
Click to collapse
I need help to unbrick an R2D2 , can you tell me where to start ?
AutoTechR2D2 said:
I need help to unbrick an R2D2 , can you tell me where to start ?
Click to expand...
Click to collapse
start here my list https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
droid wiki http://droid.koumakan.jp/wiki/Welcome
read how to boot to recovery and bootloader, flash sbf
you will need sbf, rsd lite, and moto driver installer
find those in my list
or use ezsbf for d2, easiest but you will lose r2d2 theme and sounds, but you won't need sbf, drivers, or rsd lite
Hey guys,
Has anybody attempted to flash Fido/Rogers RAZR HD XT925 to Retail Brazil 4.0.4?
I get the error:
failed to hab check for devtree: 0x56
Using RSD 6.1.5. Bootloader is locked.
I had to reflash Rogers firmware (which flashed ok with minor xml modification).
Thank you.
zzzn00bzzz said:
Hey guys,
Has anybody attempted to flash Fido/Rogers RAZR HD XT925 to Retail Brazil 4.0.4?
I get the error:
failed to hab check for devtree: 0x56
Using RSD 6.1.5. Bootloader is locked.
I had to reflash Rogers firmware (which flashed ok with minor xml modification).
Thank you.
Click to expand...
Click to collapse
Bootloader is locked means bootloader is locked. Either stay on Rogers firmware, or go to motorola's website and request a bootloader unlock code. THIS WILL VOID YOUR WARRANTY. Just so you know.
Go here if you wish to proceed. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
EdwardN said:
Bootloader is locked means bootloader is locked. Either stay on Rogers firmware, or go to motorola's website and request a bootloader unlock code. THIS WILL VOID YOUR WARRANTY. Just so you know.
Go here if you wish to proceed. https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
So let me get this straight, even with Motorola signed firmware I can't get away from Rogers firmware to stock LATAM Brazil Retail. IIRC that was not the case with XT910?
Please confirm,
Thank you.
zzzn00bzzz said:
So let me get this straight, even with Motorola signed firmware I can't get away from Rogers firmware to stock LATAM Brazil Retail. IIRC that was not the case with XT910?
Please confirm,
Thank you.
Click to expand...
Click to collapse
Hmm. You are right, that seems odd. Try re-downloading the Brazil rom, installing the latest moto drivers from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481, and grab a copy of RSD_Lite 6.1.4
Try again, maybe one of those will fix it.
EdwardN said:
Hmm. You are right, that seems odd. Try re-downloading the Brazil rom, installing the latest moto drivers from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481, and grab a copy of RSD_Lite 6.1.4
Try again, maybe one of those will fix it.
Click to expand...
Click to collapse
Thanks, will give it a shot. :good:
Hello,
I'm quite noob [totally newbie] in android installation and all, but I have been experiencing some problem on my atrix :
- after each reboot, all that have been erased reappeared, and all that have been installed/created disappeared... like a reset at a given date, or if nothing was really persisted in memory..
=> I tried a factory reset (via menu or hard reset) : after reboot, everything is like before
=> I tried to root the phone (found tuto with 4 differents tools) ; the tools don't fail, but after reboot, rootcheck tells me 'im not rooted
So last thing to do : change rom. I've found that link
http://forum.xda-developers.com/showthread.php?t=1336232
It seems fit my needs, just wondering :
- as the tuto talks about cyanogen 7, can follow the steps and install a 7.2 instead ?
- the cyanogemod 7.2 seems to be the latest very stable rom for atrix, no ?
- the atrix 4G is called olympus on cyanognemod site right ? i'm always wondering if I pick the good stuff
- for all that tuto i won't need any root permissions ? cause as I explained above, i can't manage to get them :/
- last question, do you think I have good weapons to initiate fire ?
Thanx a lot,
any advice/help is welcome,
quentasil said:
Hello,
I'm quite noob [totally newbie] in android installation and all, but I have been experiencing some problem on my atrix :
- after each reboot, all that have been erased reappeared, and all that have been installed/created disappeared... like a reset at a given date, or if nothing was really persisted in memory..
=> I tried a factory reset (via menu or hard reset) : after reboot, everything is like before
=> I tried to root the phone (found tuto with 4 differents tools) ; the tools don't fail, but after reboot, rootcheck tells me 'im not rooted
So last thing to do : change rom. I've found that link
http://forum.xda-developers.com/showthread.php?t=1336232
It seems fit my needs, just wondering :
- as the tuto talks about cyanogen 7, can follow the steps and install a 7.2 instead ?
- the cyanogemod 7.2 seems to be the latest very stable rom for atrix, no ?
- the atrix 4G is called olympus on cyanognemod site right ? i'm always wondering if I pick the good stuff
- for all that tuto i won't need any root permissions ? cause as I explained above, i can't manage to get them :/
- last question, do you think I have good weapons to initiate fire ?
Thanx a lot,
any advice/help is welcome,
Click to expand...
Click to collapse
yeah CM 7.2 is the stablest build the Artix got (Yes the codename for the Atrix is olympus) download the file at the bottom of this http://download.cyanogenmod.org/?device=olympus and flash it normally in your custom recovery without wiping the data.
Trozzul said:
yeah CM 7.2 is the stablest build the Artix got (Yes the codename for the Atrix is olympus) download the file at the bottom of this http://download.cyanogenmod.org/?device=olympus and flash it normally in your custom recovery without wiping the data.
Click to expand...
Click to collapse
Thanx Let's try, i'll give here my feedback ... well if i'm in trouble, i'll come here to scream and cry
Okay, so I'm back, and I need help :/
I well execute the steps until RSD Lite : i've seen the work on progress, the status was PASS (I assume it's good, even if my english sometimes sucks )
So i've done the next step : at the "starting fastboot protocol support" state, i tried to run the command moto-fastboot.exe oem unlock, and got the message
INFOOEM unlock is not implemented
Click to expand...
Click to collapse
So i googled the problem, and found the topic
http://forum.xda-developers.com/showthread.php?t=1185939&page=2
Click to expand...
Click to collapse
BUT the problem, the solution seems to be exactly what i previously did, i.e use http://diamantephoto.com/IHOP_Bell.rar with RSD Lite ...
So I tried a second time, just to check, but still same... Tell me PASS, but next step remains "INFOOEM unlock is not implemented" ...
I don't know what I am missing ?
quentasil said:
Okay, so I'm back, and I need help :/
I well execute the steps until RSD Lite : i've seen the work on progress, the status was PASS (I assume it's good, even if my english sometimes sucks )
So i've done the next step : at the "starting fastboot protocol support" state, i tried to run the command moto-fastboot.exe oem unlock, and got the
message "INFOOEM unlock is not implemented"
So i googled the problem, and found the topic
BUT the problem, the solution seems to be exactly what i previously did, i.e use http://diamantephoto.com/IHOP_Bell.rar with RSD Lite ...
So I tried a second time, just to check, but still same... Tell me PASS, but next step remains "INFOOEM unlock is not implemented" ...
I don't know what I am missing ?
Click to expand...
Click to collapse
i wanna say the bootloaders still locked, you should only have to open up ADB and type (be sure to go into fasboot mode first)" fastboot oem unlock " if your problem still persists, what guide are you using? i would recommend cyanogenmods if you want to flash their rom http://wiki.cyanogenmod.org/w/Install_CM_for_olympus
Is it because it's a tutorial for a locked phone AT&T, whereas mine isn't locked ?
quentasil said:
Is it because it's a tutorial for a locked phone AT&T, whereas mine isn't locked ?
Click to expand...
Click to collapse
carrier locked? or the bootloader
Trozzul said:
carrier locked? or the bootloader
Click to expand...
Click to collapse
carrier locked ... cause I guess you are right, the RSD Lite step I did doesn't seem to unlock my bootloader
Maybe it's the same cause why I didn't manage to root the mobile, as I explained in first posrt :/
I'm gonna try your link, but the one I had seemed very well
HTML:
http://forum.xda-developers.com/showthread.php?t=1336232
quentasil said:
carrier locked ... cause I guess you are right, the RSD Lite step I did doesn't seem to unlock my bootloader
Maybe it's the same cause why I didn't manage to root the mobile, as I explained in first posrt :/
I'm gonna try your link, but the one I had seemed very well
HTML:
http://forum.xda-developers.com/showthread.php?t=1336232
Click to expand...
Click to collapse
yup cant Root your devices with a locked bootloader carrier lock does not matter towards all this nerd entities
Trozzul said:
yup cant Root your devices with a locked bootloader carrier lock does not matter towards all this nerd entities
Click to expand...
Click to collapse
yes, but that is weird cause I'm NOT locked carrier ... So i should have been able to root without problem :/
quentasil said:
yes, but that is weird cause I'm NOT locked carrier ... So i should have been able to root without problem :/
Click to expand...
Click to collapse
well if you unlocked the boot-loader before you wouldn't have had a problem.
Ok i begin to understand a little Well, i'm slow, but it's late
So the tuto I had was for locked carrier so I guess this is why they expected to get a number when calling moto-fastboot.exe oem unlock...
Since mine is not, INFOOEM unlock is not implemented is the expected result Means my bootloader is unlocked, i'm right ?
The link you gave me is more clear to me
So i tried the next step, to flashClockworkMod Recovery
fastboot flash recovery your_recovery_image.img
Click to expand...
Click to collapse
but i have a beautiful
Failed to process command flash:recovery error (0x180002)
Click to expand...
Click to collapse
Googled a little, tried to change the name and path of the recovery, but didn't work :/
Ok, i just get a little confused now ...
On the tutorial of cyanogenmod, they say
On the computer, open terminal and run the following command:
fastboot oem unlock
If a message appears claiming that "INFOOEM lock is not implemented", you are done.
Click to expand...
Click to collapse
So I assumed that my bootloader was unlocked
But when i search on google the error Failed to process command flash:recovery error (0x180002), i often find that it means that the bootloader isn't unlocked ...
More crazy, sometimes I read that on Motorola Atrix 4G soemtimes bootloader isn't unlockable, and the solution is to flash a sbf with RSD Lite .... What I also did when i followed the first tutorial http://forum.xda-developers.com/showthread.php?t=1336232
So now, i'm totally confused
quentasil said:
Ok, i just get a little confused now ...
On the tutorial of cyanogenmod, they say
So I assumed that my bootloader was unlocked
But when i search on google the error Failed to process command flash:recovery error (0x180002), i often find that it means that the bootloader isn't unlocked ...
More crazy, sometimes I read that on Motorola Atrix 4G soemtimes bootloader isn't unlockable, and the solution is to flash a sbf with RSD Lite .... What I also did when i followed the first tutorial http://forum.xda-developers.com/showthread.php?t=1336232
So now, i'm totally confused
Click to expand...
Click to collapse
the bootloader should be unlockable as for the "[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX" its from 2011 so its a little old, i would stay with the cyanogenmod guide. about all of the time they are very clear with their guides.
if you get INFOOEM lock is not implemented that should mean your bootloader is unlocked,
INFOOEM unlock is not implemented would be a locked bootloader.
Trozzul said:
the bootloader should be unlockable as for the "[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX" its from 2011 so its a little old, i would stay with the cyanogenmod guide. about all of the time they are very clear with their guides.
if you get INFOOEM lock is not implemented that should mean your bootloader is unlocked,
INFOOEM unlock is not implemented would be a locked bootloader.
Click to expand...
Click to collapse
oh yes of course, makes so much sense now but i didn't notice INFOOEM lock/unlock variant
so I have INFOOEM unlock, so my bootloader is still locked, so the message I get when trying to flash the recovery is logical.
Thanx for making it obvious
Now I need to find why my bootloader is still locked, since I used RSD Lite with a sbf, which told me "PASS" after procedure :/
quentasil said:
oh yes of course, makes so much sense now but i didn't notice INFOOEM lock/unlock variant
so I have INFOOEM unlock, so my bootloader is still locked, so the message I get when trying to flash the recovery is logical.
Thanx for making it obvious
Now I need to find why my bootloader is still locked, since I used RSD Lite with a sbf, which told me "PASS" after procedure :/
Click to expand...
Click to collapse
Ok, seems RSDlite doesn't achieve to install new unlockable bootloader ... The process is very quick compare to a tuto i've seen, and at the end i have always the INFOOEM unlock ....
Is there any way to check the bootloader version once boot up ? But I suspect that, as the factory reset didn't work, the same thing happen when I try to put a new boatloader....
quentasil said:
Ok, seems RSDlite doesn't achieve to install new unlockable bootloader ... The process is very quick compare to a tuto i've seen, and at the end i have always the INFOOEM unlock ....
Is there any way to check the bootloader version once boot up ? But I suspect that, as the factory reset didn't work, the same thing happen when I try to put a new boatloader....
Click to expand...
Click to collapse
theres a mode like Hboot for htc devices on motorola phones, i dont know how to get into it though, mess witth the combinations.
---------- Post added at 01:57 PM ---------- Previous post was at 01:45 PM ----------
if we run out of ideas you can try this method i found http://www.atrixforums.com/forum/mo...ocking-bootloader-installing-custom-roms.html
Trozzul said:
theres a mode like Hboot for htc devices on motorola phones, i dont know how to get into it though, mess witth the combinations.
---------- Post added at 01:57 PM ---------- Previous post was at 01:45 PM ----------
if we run out of ideas you can try this method i found http://www.atrixforums.com/forum/mo...ocking-bootloader-installing-custom-roms.html
Click to expand...
Click to collapse
Ok, i'll check this tomorrow ... but at first look the flash of sbf seems the same, except maybe for the sbf file itself...
Hi all
Well I have a xt926....which is now on 186.43.15...... Stock
After the last patch over air....does not detect my sim any more....replaced with several other sims....and no one is detected....mine is working on another phone....
Have any ideabon whatvis going on?
Regards
do a factory data reset
JoseBerga said:
do a factory data reset
Click to expand...
Click to collapse
Already did....no changes....
Power off- on....airplane mode ......etc....hards reset....
jgax said:
Hi all
Well I have a xt926....which is now on 186.43.15...... Stock
After the last patch over air....does not detect my sim any more....replaced with several other sims....and no one is detected....mine is working on another phone....
Have any ideabon whatvis going on?
Regards
Click to expand...
Click to collapse
your the second person i have seen this happen to i would say reflash the 186.43.15 with rsd to see if that fixes it here use @SamuriHL s full script http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083
wait before you do that had you radio unlocked before? you may need to unlock your radio again if you on another carrier other than vzw
billycar11 said:
your the second person i have seen this happen to i would say reflash the 186.43.15 with rsd to see if that fixes it here use @SamuriHL s full script http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083
wait before you do that had you radio unlocked before? you may need to unlock your radio again if you on another carrier other than vzw
Click to expand...
Click to collapse
Will try today and report back.....I was sim unlocked before ota.....also unlocked after....but no lucky...
Is needed to have the bootloader unlocked to reflash again?
jgax said:
Will try today and report back.....I was sim unlocked before ota.....also unlocked after....but no lucky...
Is needed to have the bootloader unlocked to reflash again?
Click to expand...
Click to collapse
no you do not need to be unlocked to flash with rsd but before reflashing try sim/radio unlocking your phone again with this http://forum.xda-developers.com/showthread.php?t=2389740 to see if that is the problem
billycar11 said:
no you do not need to be unlocked to flash with rsd but before reflashing try sim/radio unlocking your phone again with this http://forum.xda-developers.com/showthread.php?t=2389740 to see if that is the problem
Click to expand...
Click to collapse
Thanks Billy
It seems to work fine now....it detect my sim again...just will unlock for gsm networks.....
Im really glad to have support like you guys..
Thanks Again.
jgax said:
Thanks Billy
It seems to work fine now....it detect my sim again...just will unlock for gsm networks.....
Im really glad to have support like you guys..
Thanks Again.
Click to expand...
Click to collapse
glad your up and running
new to the phone, bought yesterday for temp use, same thing happened, i just removed the sim, did a factory reset and now it works.
Glad to see you got this resolved. Hoping I don't have this issue when I update.
Mod Edit : Thread closed. Xda is not a place to sell services of any kind.
GJ!
I've actually been trying to wrap my head around all of that, until I cam across that experimental way to unlock,
Nokia customer support wasn't helpful either.
Thanks for the clear instructions
And it worked +1
Will try it, if there is way @heineken78 I send info
Powered by Nokia 8
I don't need your imei )
Please I am begging the senior members please, someone should help me..my phone has been bricked for 2 months now..my Nokia 6 ta-1003.. it's stuck on QLD 900E... PLEASE HOW DO I resolve this myself...I have been without a phone since... someone should help me out of this nightmare..it doesn't come on,just only shows the notification lights and QLD 900E on device manager... awaiting a positive response..thanks
banijam said:
Please I am begging the senior members please, someone should help me..my phone has been bricked for 2 months now..my Nokia 6 ta-1003.. it's stuck on QLD 900E... PLEASE HOW DO I resolve this myself...I have been without a phone since... someone should help me out of this nightmare..it doesn't come on,just only shows the notification lights and QLD 900E on device manager... awaiting a positive response..thanks
Click to expand...
Click to collapse
Your case is lost boot, must disassemble machine and TP. My Nokia 6 (TA-1000) has been and must remove the machine to TP.
banijam said:
Please I am begging the senior members please, someone should help me..my phone has been bricked for 2 months now..my Nokia 6 ta-1003.. it's stuck on QLD 900E... PLEASE HOW DO I resolve this myself...I have been without a phone since... someone should help me out of this nightmare..it doesn't come on,just only shows the notification lights and QLD 900E on device manager... awaiting a positive response..thanks
Click to expand...
Click to collapse
https://alephsecurity.com/2018/01/22/qualcomm-edl-1/
The picture in this topic told you where to short. It's on the bottom. Connect your phone with both pin shorted, you'll enter Qualcomm 9008 directly. Then you should know what to do next.
Interesting. I will have to look at it with time, it seems to be a bit of a risky method still.
Can I flash any custom Recovery? And how would I do that?
Sörnäinen said:
Interesting. I will have to look at it with time, it seems to be a bit of a risky method still.
Can I flash any custom Recovery? And how would I do that?
Click to expand...
Click to collapse
i have used this method to unlock and works without any problem.(ta-1033 PLE)
but i have the same questions
Can I flash any custom Recovery? And how would I do that?
parageria said:
Can I flash any custom Recovery?
Click to expand...
Click to collapse
Nope, it must be made for your model specifically.
revanmj said:
Nope, it must be made for your model specifically.
Click to expand...
Click to collapse
thanks
i mean any of nokia 6 that exist in others threads
It works ! Thank you sir!
https://drive.google.com/file/d/1eOK7uE_te7moCG6-io8UgFuEcY_arL5i/view?usp=sharing
https://drive.google.com/open?id=1DW_R4CHwHVqqIlEtHbBmaLn28txs-wE5
https://drive.google.com/open?id=1pOrIsxB0NB9Y6_DkQlf1Y9TreTgKWw0a
https://drive.google.com/open?id=1gvWHZtbvFTlHzQ-QR--8hjygEJyUmAeN
how to relock the bootloader？
If i unlock the bootloader on my TA-1033 , can i install the twrp ?
Aventurepix said:
If i unlock the bootloader on my TA-1033 , can i install the twrp ?
Click to expand...
Click to collapse
of course, yo can do it
hawwin88 said:
of course, yo can do it
Click to expand...
Click to collapse
I have a problem with my TA-1033 , the bootloader is unclock but when i flash twrp , when i reboot in recovery , it's not twrp but it's the original recovery , why ?
Aventurepix said:
I have a problem with my TA-1033 , the bootloader is unclock but when i flash twrp , when i reboot in recovery , it's not twrp but it's the original recovery , why ?
Click to expand...
Click to collapse
You should install TWRP with command in fastboot mode, have u done with it ? If not yet , you must do it .. Please read another post from @Hikari about root
---------- Post added at 01:32 AM ---------- Previous post was at 01:24 AM ----------
Nokia 6（2018）will work?[/QUOTE]
I have a simple question,
Right now i'm on Android 8.0.0 on my TA-1033 , can i flash TWRP or i need to downgrade the bootloader ?