Hello guys, yesterday I put my Moto X (1058) to 4.2.2, everything went right but after installing the rom (Putting the Google login, and install applications, update asked the camera) so I downloaded it and was installing cellular rebooted and got the green little robot, then the cell phone completely shut down, waited a few minutes and did not care (I was connected to the USB port on your notebook).
I was totally desperate because I need to communicate with my parents (study in the capital and my parents are from inside) I tried pressing the power button plus the volume at least 30 seconds and nothing I bought a wall charger and tried did not work, at least at fastboot but not to call this occurs.
Please I need help, I will be eternally grateful
What you did before flash 4.2.2?
You was on kit kat?
Please read this and tell me if you did the same procedure, because I killed my moto X too (really and totally hard brick)
http://forum.xda-developers.com/showthread.php?t=2548867
Now i've replaced it
d14gvn said:
What you did before flash 4.2.2?
You was on kit kat?
Please read this and tell me if you did the same procedure, because I killed my moto X too (really and totally hard brick)
http://forum.xda-developers.com/showthread.php?t=2548867
Now i've replaced it
Click to expand...
Click to collapse
given he doens't type great english, i believe in there he said something about being able to get into fastboot mode so its not hard bricked. But i'm not really sure if he did say that or not because he also said something about pressing the power button alot.
anyway, if you can get into fastboot buddy, just find the rsd lite back to stock thread and do that. if you can't get to fastboot, you are in the same boat as d14 and hard bricked that phone. you can try replacing it if they will let you but thats your only shot.
Related
Hello. Well to start off I had recently rooted my Droid2 which was running the OTA GB. So I started looking for roms like I use to with froyo and the leaked GB. Was looking for something to change the battery life frame poor to great. Anyway I came upon Cyanogenmod's Rom for Droid 2 For the ota gb. I made a nandroid back up, downloaded it and was ready to flash. Seconds away in boot recovery and while i was looking for the file before I think I hit "apply update" instead of "search for zip file on scdard(or what ever sentence it says) and i got it but it started loading an update. I was like wtf kinda freaked out and I did a battery pull . Now my phone stays at the M boot logo and i have no way to go back. I heard the SBF for GB ota isnt her yet . if anyone can help I would be grateful. Plz Help
Things I've tried/
1.Battery Pull.
2.Hold power button + hold X(doesnt work like froyo Poo)
3.Tried going back with rsdlite 5.3.1 with moto drivers(it won't show my device ;'( )
4.Left this message on xdadev / please help
SOLVEd
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution
T3viin said:
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution
Click to expand...
Click to collapse
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?
Charge your battery in another phone like yours. Borrow someones spare battery. Take battery to verizon store and see if they can charge it somehow. There is a thread on here somewhere on how to do a hack job on your cable and hook the wires directly to your battery and charge it independent of the phone. I can't post a link so I hope you can find it by searching.
Sent from my DROID2 using XDA App
dmeadows013 said:
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?
Click to expand...
Click to collapse
I've had this problem 4 times in the last week. I used a terminal based OS to SBF using ADB.
And in the same step I re rooted my phone. Whole thing takes about 15-20 minutes.
The steps are on the CMWiki.
Hello Guys,
I bricked my Milestone 2 when trying to install the update for version Android 2.3.
It appers the Google logo when the phone starts, but it shuts off by it self.
When I try the recovery mode:
I get to it, but when I select the option of wipe data and reset to factory, does it start, but shuts off in the middle of the progress.
(When does it shut, I can turn back on easy)
When I try the bootloader:
Stuck saying that battery is low Can't program.
(I left the phone charging all day and I get the same message)
I do not know what to do anymore, some of the users here, says that is the battery.
But, the battery is bad or the phone is not charging?
When I plug the charger, the light turns on.
What do you guys think?
I already see the option in use the Nandroid Recovery, but I'm nor sure how to do it...
I do not have any friend with the same phone, so I will have to buy another battery or a universal charger, that I can charge the battery with out the phone.
Thanks in advance for your help.
Jeferson.
Wow, that was there so many times. For instance:
http://forum.xda-developers.com/showthread.php?t=1344740
or http://forum.xda-developers.com/showthread.php?t=1363918
in the sum some facts:
- you can't charge battery in bricked milestone 2
- you MUST have some charge in battery for SBF flashing via bootloader
1) you have to charge battery
2) you have to flash SBF via RSDLite
Milestone 2 hardbrick
First I upgraded the milestone 2 kitkat then disappeared until it was trying to downgrade and there it all began. No button works x vol + vol - @ all possible combinations already tried the rsd lite does not recognize the phone, adb and fastboot also not the phone, but makes up the sbf_flash is waiting for the phone in the end, the only thing q works is the LED side of the micro usb is solid and sometimes q could use rsd she appeared sw update in progress so but after that it also could not switch on the phone. I read a lot and could not find any case equal to staff]
Please help me
God bless us all ..
Thanks Hemerson
sorry about my english
google tradutor
I am a milestone 2 owner and I messed it up.
I came from 2.3.6 GB Retail ROM, and run a bootstrap first time to go to CM7.2, and it is ok.
After a time, I decided to go to CM9.
And I run the bootstrap for second time.... so I got it bricked.
What I tryed before to ask?
1. Power up + Up arrow - doesnt work
2. Power up + x - Goes to blank screen
3. Power up + Volume Down + Camera = Bootloader OK
And a lot of another combinations that doesnt work.
The problem is the Phone isnt recognized by PC, I tryed using USB_Drivers_Bit.... 3 or 4 different versions...
I tryed Motorola motocast drivers...
Moto Helper (from first to last version)
And everytime is the same thing "your device can't be recognized".
I am thinking about to try ADB drivers, and at least Flash a SBF from linux, with SBF_FLASH scrypt.
And for worse, my battery is down.
Can someone give me a little help?
mmkah said:
I am a milestone 2 owner and I messed it up.
I came from 2.3.6 GB Retail ROM, and run a bootstrap first time to go to CM7.2, and it is ok.
After a time, I decided to go to CM9.
And I run the bootstrap for second time.... so I got it bricked.
What I tryed before to ask?
1. Power up + Up arrow - doesnt work
2. Power up + x - Goes to blank screen
3. Power up + Volume Down + Camera = Bootloader OK
And a lot of another combinations that doesnt work.
The problem is the Phone isnt recognized by PC, I tryed using USB_Drivers_Bit.... 3 or 4 different versions...
I tryed Motorola motocast drivers...
Moto Helper (from first to last version)
And everytime is the same thing "your device can't be recognized".
I am thinking about to try ADB drivers, and at least Flash a SBF from linux, with SBF_FLASH scrypt.
And for worse, my battery is down.
Can someone give me a little help?
Click to expand...
Click to collapse
Well, you can't bootstrap on a custom ROM, you brick your phone, I guess that's a lesson learned the hard way
The good news is that your problem can be easily solved, use a universal charger to fully charge your battery, then you can get to the bootloader mode with up arrow + power button and flash the stock sbf again
[SOLVED]
Yes man, you're right. Let me talk about something
I sent my ML2 to tecnical assistance.... here at my city....
I think that they had try to pass a new rom or something like this.... without sucess.
They said me that it is a motherboard problem.
I took my phone back, I came to home and try to charge up,.... and it is working...(strange).
at 100% I tryed my rsdlite, and passed a full rom.... 2x
after I went to recovery mode (it was blocked at the first brick) and I did a wipes and wipes.....
IT IS BACK AGAIN, WITHOUT COST. FOR FREE!!
I am a very lucky man, very lucky man.
thank you CAESARIVS you are right, the only thing that we need is a fully battery, I have learned a lesson (at hard way).
mmkah said:
I sent my ML2 to tecnical assistance.... here at my city....
I think that they had try to pass a new rom or something like this.... without sucess.
They said me that it is a motherboard problem.
Click to expand...
Click to collapse
I think they changed a new motherboard so you can do anything when you get it back.
mmkah said:
Yes man, you're right. Let me talk about something
I sent my ML2 to tecnical assistance.... here at my city....
I think that they had try to pass a new rom or something like this.... without sucess.
They said me that it is a motherboard problem.
I took my phone back, I came to home and try to charge up,.... and it is working...(strange).
at 100% I tryed my rsdlite, and passed a full rom.... 2x
after I went to recovery mode (it was blocked at the first brick) and I did a wipes and wipes.....
IT IS BACK AGAIN, WITHOUT COST. FOR FREE!!
I am a very lucky man, very lucky man.
thank you CAESARIVS you are right, the only thing that we need is a fully battery, I have learned a lesson (at hard way).
Click to expand...
Click to collapse
I'm really glad you have your phone back
Sent from my MotoA953 using Tapatalk 2
DolphinWing said:
I think they changed a new motherboard so you can do anything when you get it back.
Click to expand...
Click to collapse
No,
they said me the mother cost almost a new phone, and they gave up.
mmkah said:
No,
they said me the mother cost almost a new phone, and they gave up.
Click to expand...
Click to collapse
i always flash the sbf if i brick the ms2
I have big problem with my MS2. I flashed it via the RSD with some 2.3.4 rom (yes, I know, it's not the best rom to choose, but I did it...) and...
I have bootlop and no way to go into recovery. I tried everything, but my keyboard was dead (just few keys, but including X). Then I tried to swap keyboards with one from working MS. Still nothing. How to wipe that phone?! I have no idea. Please help.
DJPreZes669 said:
I have big problem with my MS2. I flashed it via the RSD with some 2.3.4 rom (yes, I know, it's not the best rom to choose, but I did it...) and...
I have bootlop and no way to go into recovery. I tried everything, but my keyboard was dead (just few keys, but including X). Then I tried to swap keyboards with one from working MS. Still nothing. How to wipe that phone?! I have no idea. Please help.
Click to expand...
Click to collapse
Are you sure is a keyboard problem? Try taking the battery out, then, press and hold the X key, and put on the battery while holding it... you should get the android logo with an exclamation sign, then press both volume buttons...
If you try to get into bootloader (with the up arrow), can you get into it?
Yes. That was a keyboard problem. I swaped another keyboard and it's working now (x at startup, then vol up and down + wipe everything)
Edit after few hours (and downgrading back to froyo)... Keyboard don't work :/ QWEADX and few more. On both old and new Milestone2 keyboard and on a Milestone1 keyboard. Maybe the flex cable is dead?
I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .
OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.
Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Niko. said:
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Click to expand...
Click to collapse
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
htto said:
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
Click to expand...
Click to collapse
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Niko. said:
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Click to expand...
Click to collapse
Too bad Anyway, did you try 8. from here, that is
"
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
"? Also holding Power and Vol-Down while inserting battery is said to work.
I wonder if there is an SBF that also flashes cache and userdata partitions...
Nope, it just stays black-screened.... It only works if i do VOL-UP for bootloader mode, but that doesnt help
Umm, as a shot into the blue: Did you try to reinstall the Defy drivers from Motorola? It seems that missing those hinder RSD lite from detecting the Phone as MB52x and instead just show the Processor identification, i.e. "S Flash OMAP3630"
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Sent from my MB526 using Tapatalk
thekguy said:
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Click to expand...
Click to collapse
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
htto said:
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Niko. said:
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Click to expand...
Click to collapse
Umm, according to this thread it is supposed to be this one.
The GR vs CN maybe doesn't make a difference, but maybe the P022_A022 vs. P015_A030?
Doesn't a working phone portal allow for somehow to get logs/adb etc?