I have droid razr Verizon USA unlocked to India
previously it has ICS4.0.4
so tried updating to jelly bean following steps posted in one of the xda thread
but it is not successful
so i tried to reflash using rsd lite to my stock rom ie:ics
but not successful flash failure and customer id error is coming
I also went to motorolla service center in india but they said mothboard is gone have to purchase motherboard costing 18000 Rupees
but seeing the post i have still some hope that cid.img can be restore as my phone is going in ap fastboot only but battery is not charging
when i plug in charger it boots in ap fastboot mode
so plz give me the way to solve it
AW: [Q] How to restore Cid.img via windows Command Prompt
What's the Error (FlashFailure System / Webtop etc...)
You need an new Motherboard if you've lost your CID Backup and wanna get rid of the Customer ID Error, but not to get your Phone back to life.
I use my RazR without CID for one year now and I flashed a lot during that time, with RSD, too.
Sent from my XT910
CID is unique ; like, if you've lost yours there is nothing you can do.
Just boot trough bptools and get used to it ; otherwise do what hsd-pilot said
Restoring CID
androtech.n said:
I have droid razr Verizon USA unlocked to India
previously it has ICS4.0.4
so tried updating to jelly bean following steps posted in one of the xda thread
but it is not successful
so i tried to reflash using rsd lite to my stock rom ie:ics
but not successful flash failure and customer id error is coming
I also went to motorolla service center in india but they said mothboard is gone have to purchase motherboard costing 18000 Rupees
but seeing the post i have still some hope that cid.img can be restore as my phone is going in ap fastboot only but battery is not charging
when i plug in charger it boots in ap fastboot mode
so plz give me the way to solve it
Click to expand...
Click to collapse
I understand that you erased your CID without making a backup of it at first, if you have a backup then restore when in AP fastboot mode by fastboot flash cid cid.img.
If you did not make a backup fromyour Phone CID which I believe it's the case, then as HDpilot is saying we're all living with our phones with this CID error and happy with it because nothing stop us from flashing any ROM from any different regional location.
I have cid.img backup
kkhadr said:
I understand that you erased your CID without making a backup of it at first, if you have a backup then restore when in AP fastboot mode by fastboot flash cid cid.img.
If you did not make a backup fromyour Phone CID which I believe it's the case, then as HDpilot is saying we're all living with our phones with this CID error and happy with it because nothing stop us from flashing any ROM from any different regional location.
Click to expand...
Click to collapse
I have cid.img of 512kb backup but how to restore to it in ap fastboot mode as my phone is not working so can restore using Command prompt of windows
Plz provide step by step procedures
androtech.n said:
I have cid.img of 512kb backup but how to restore to it in ap fastboot mode as my phone is not working so can restore using Command prompt of windows
Plz provide step by step procedures
Click to expand...
Click to collapse
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash cid cid.img
allow-mbmloader-flashing-mbm.bin file :good:
que
Thankyou brother
but can you show the step by video if possible plz as i have tried to update by following the step in video and got stuck
PLZZZ its a month i am without my phone
Trying to load another cid
Did some1 ever try to do it? flashing another cid. for Ex. what happens if I try to flash a cid of an european razr since mine also EU too.
I deleted my cid when I softbricked my phone and its disturbs me everytime when I see that sh*t on my screen.
I also got similar problem((((
tried to flash JB. Was on ICS....... Bricked((((
Device - XT910s Korea SKT
But when I am trying to erase CID, the fastboot fails as the bootloader is not unlocked. I hope my CID is not erased...
Now will try to flash stock SKT.KR xml firmware.
Will tell you the result
Related
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
rp2gardner said:
Failed to boot 2
Starting RSD mode.
I tried to flash the new Ninja Rom from the Gingerblur rom. I am now stuck on the dual core screen with the message above stuck there. Someone please help, I looked through the forms but it seems like I should be able to get into recovery still, which I cannot... If you need any other info please let me know....
Click to expand...
Click to collapse
Were you unlocked before trying to flash Ninja rom?
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
That is why, your bootloader has to be unlocked.
Sent from my MB860 using XDA Premium App
rp2gardner said:
unlocked... no at least I dont think? Obviously I was rooted but unlocked i dunno...
Click to expand...
Click to collapse
Ah ok... gingerblur was a pseudo-rom... made before we were able to install custom roms because we couldn't unlock our bootloader. That changed last month when devs figured it out and thus the newer custom roms. To install them you need to unlocked your bootloader.
Please read this thread for information on how to unlock
http://forum.xda-developers.com/showthread.php?t=1136261
Now, since you're already softbricks, running that may not work right now. BUT it's start.
My suggestion- read the thread, follow the instructions and see if that gets you to boot up properly after running the oem unlock.
If not, then download a fresh stock 1.8.3 SBF form the development thread and RSD flash that.
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
rp2gardner said:
Ok thank you for your help, will post a question if I come to one. How would I download the stock 1.8.3 SBF if I am stuck on the boot screen? Im feeling like Im in over my head, Paypal donation to anyone who can walk me through this....
Click to expand...
Click to collapse
Stock SBFs are in the development forum as well.
I guess first things first, do you have the tools needed
Do you have or know how to use RSD?
How about Fastboot?
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
rp2gardner said:
Just downloaded RSD lite and flashed the SBF..
"Open and extract the Fastboot package from above" is the step I am on.. Not sure where to go from here.
The phone rebooted to the same screen that it was at before with the error message but says PASS in RSDLite for the sbf flash
Click to expand...
Click to collapse
Which SBF? The pudding/unlock?
If you flashed the pudding SBF, then you need to do the fastboot steps next.
Did you download and unzip the fastboot package to your computer?
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Ok, I still have the failed to boot 2, but I am now getting the Starting Fastboot protocol support. I dont understand this step..
Type the following command:
fastboot oem unlock
rp2gardner said:
I did, I just dont know what to do with fastboot. Do I run it or what?.. THANKS A TON BY THE WAY...
Click to expand...
Click to collapse
let's say you saved and extracted the fastboot files to c:\fastboot
then you have to open up CMD (start - run - cmd )
then cd to the directory it's saved (in this example c:\fastboot )
Now you have to get your phone into fastboot mode (directions are in the link), but in short, as you turn on your phone, hold the down button. THen it should say fastboot, then hit volume up, should say entering fastboot
Then back on computer in the command window
while your in the fastboot directory
type the oem unlock command (specific command in the instruction).
after it's all done, type fastboot reboot.
I have to go now for a while, but if all that doesn't work. I suggest flashing via RSD the 1.83 SBF with Pudding built in.
The download is in the pudding thread near the top "1. All phones If you have unlocked then try to use 2.3.4 update zip from Motorola servers, then revert back to a "pre-unlock" version(1.8.3 or earlier on ATT) you will get bricked! Do not use the OTA via experimental servers and revert to older versions WITHOUT pudding preinstalled in your sbf.
ATT ONLY Get your 1.8.3 with pudding from gitbrew or multiupload."
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
rp2gardner said:
I cant figure out where to type the command in (fastboot oem unlock) i have the screen that came up when i located the fastboot. It has a list of commands, but nothing about oem unlock...
Click to expand...
Click to collapse
Is your phone in fastboot mode and connected?
All you gotta do is just type the command in the command window
C:\fastboo\ fastboot oem unlock
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Did u try doing factory reset from boot menu
Sent from my MB855 using xda app-developers app
Yes i did try that along with every other option given system still not booting up... but another strange thing ive noticed is that the android recovery is now letting me choose what zip i want to install from my sd card although i cannot because everything keeps failing the signature check. Has anyone been in this same situation?
I think i flashed the ap20bl.img with sv1 but i havnt flashed the microboot because i didnt know what command to issue in fastboot mode. for the bootloader i typed something along the lines of "fastboot flash rdl3.bin rdl3_unlocked.smg" then i think it restarted to only the moto logo was there and i typed fastboot devices it showed my phone so i took the cg file from derpunlock and typed a command like fastboot flash boot cg42_000somthing.smg it said ok finished... ???
sunny530 said:
Has anyone ever seen this before? I have reflashed stock recovery to the phone and before i could switch options in the boot menu i was stuck to only rsd or fastboot. I am on 2.3.5 I sent rdl3 to the phone it restarted in bootloader or fastboot just a moto logo i sent the fastboot oem unlock command, peices of derpunlock and also a system.img. now i can choose android recovery in my boot menu but system still wont load.
Click to expand...
Click to collapse
are you saying you're on 2.3.5? if you are, your bootloader is permanently locked. it won't do any good to try and unlock it, unless you don't mind bricking. otherwise i have never seen this error before.
if you are on 2.3.5 i'd recommend flashing the electrify 2.3.5 sbf method to hopefully unbrick and return to stock.
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
sunny530 said:
Thanx for the reply na7q but I am pretty sure when software says unrecoverable error you have just killed it. When you torpedo root doesnt that kill the xorg server? as soon as its dead BAM!!! your rooted lol i would really like it if some very knowledgeable people on this subject would take a look at this and if they all tell me to do the same thing then 2.3.5 electrify here i come, However, i am not concerned of getting my phone in working order if my phone remains dead for the next few days i dont mind as long is it contributes to this bootloader being unlocked.
Click to expand...
Click to collapse
with 2.3.5 you aren't unlocking anything. can almost guarantee it! it's going to take a miracle! i'd say just restore it with the SBF if possible and continue on with life haha. i rooted like a year ago so i don't remember anything about it at this point haha. the only thing that was important was unlocking the bootloader! we need a breakthrough on that for these locked users. that miracle hasn't happened yet. or even gotten close.
Try flashing signed boot.img. This seems to me like failed to boot 2 in other words.
You can flash almost anything into the phone, the signature is checked after reboot, so "flashing ok" in fastboot is normal feedback, sometimes even if it's not ok (radio).
Also with recovery, you can choose whatever zip you want, but when you hit install, signature is checked.
Well you see i receive no failure to boot 1-4 i just get stuck at the moto dual core screen with nothing written at the top. Is it possible that i flashed the bootloader sucsessfully and did not flash the microboot? i didnt know the command to issue to flash microboot. The unrecoverable bootloader error seems interesting to me how would i find out what kernal i should/can flash and what would be the command would it be in fastboot? can i install a system.img via recovery or install bootstrap through fastboot or stock recovery?
Is it possible to flash american CID via bmm instead of the original uniqe cid of my xt910?
It will help people to flash the update via stock recovery without any need to bmm...
Only pushing the kernel and flash.
thanks... :highfive:
if its possible, can someone who handle xt912 backup his CID and upload it?
UduBobo said:
Is it possible to flash american CID via bmm instead of the original uniqe cid of my xt910?
It will help people to flash the update via stock recovery without any need to bmm...
Only pushing the kernel and flash.
thanks... :highfive:
if its possible, can someone who handle xt912 backup his CID and upload it?
Click to expand...
Click to collapse
AS long i know, CID is a unique customer identification...
YOu can't use someone else cid ; unless the person wants to give information about its phone to you (i think i'm not sure)
What you want to do ? Flash to JB ?
pablobhz said:
AS long i know, CID is a unique customer identification...
YOu can't use someone else cid ; unless the person wants to give information about its phone to you (i think i'm not sure)
What you want to do ? Flash to JB ?
Click to expand...
Click to collapse
yes, and remove all the CID FAIL thing.
Got it.
Well, i don't think someone will upload a cid for you - as i said it's a personal unique number.
You don't have any backup ?
If u don't... Get used to boot trough bp tools...
Sent from my MOTOROLA RAZR using xda app-developers app
Don't get troubled, and go the safe way!
Install bmm 0.3.4, backup CID, erase CID, flash kernel from bmm, flash baseband (optional), enjoy; but you knew that already.
bmm 0.3.4 gets its way to avoid bp tools so no worries there with CID error.
It is already as easy as it needs to be :good:
PS.: from my understanding the CID is attached to chipset's imei so you can't put whatever CID you want; just your device's one, maybe this answers your question.
osval. said:
Don't get troubled, and go the safe way!
Install bmm 0.3.4, backup CID, erase CID, flash kernel from bmm, flash baseband (optional), enjoy; but you knew that already.
bmm 0.3.4 gets its way to avoid bp tools so no worries there with CID error.
It is already as easy as it needs to be :good:
PS.: from my understanding the CID is attached to chipset's imei so you can't put whatever CID you want; just your device's one, maybe this answers your question.
Click to expand...
Click to collapse
I didn't knew about this trick
Thanks
Just remember to flash "JB kernel-based roms" ONLY right after flashing kernel, otherwise it will not boot, if you want to get back to ics you must flash an ICS kernel to boot, you can backup your kernel before flashing the jb kernel but with erased cid you can flash any ics kernel if you forgot to do that
the safer bet will be keeping your stock ics on main system, an do all the flashing stuff in 2nd system (must activate first, there are tutorials for that) so you can easily come back flashing ics kernel and switch to system 1 if anything goes wrong.
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
lextacy said:
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
Click to expand...
Click to collapse
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
shimp208 said:
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
Click to expand...
Click to collapse
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
lextacy said:
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
Click to expand...
Click to collapse
Glad I could help you out ! It must be a bad boot image then that you flashed, but that shouldn't prevent you from accessing the bootloader. When you get your new phone and root it you should be able to pull that stock boot image and then get your old phone working again. As always any questions let me know !
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
JackSlaterIV said:
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
Click to expand...
Click to collapse
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
shimp208 said:
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
Click to expand...
Click to collapse
Thanks, I saw but there is no answer there.
Hey Guys,
I got a few LG G5 h850 and was thinking to create and maintain a "Master-ROM" (LOS14.1, Magisk 17.2 ...) with a" Mother Device" so I can back it up with NanDroid/by TWRP and TiBackup, and flash it to all Children devices after.
While trying to restore the TWRP Backup to the first phone, I was an idiot and marked all partitions. Guess I should have left out some:
After restoring the Backup and Booting I get the "Your device is corrupted" Error.
With a Fastboot Linux Host machine I tried flashing TWRP again, but the device is locked against flashing..
The first unlocked bootloader is locked again:
When I tried to flash the unlock.bin again, I discovered that the IMEI of the "Mother-ROM Device" got implemented,
causing a difference in IMEI vs. OEM ID, causing the unlock.bin not to work.
I ****ed up.
I researched and tried "$ fastboot oem writeimei 123456789012347" with Linux ADB shell, but that command is only for a modified fastboot libary.
1. Question:
Well - anybody have any idea how to write the original IMEI into the device again, so I can fastboot flash unlock, fastboot flash recovery it again?
In the meantime I will try if the LGs website will generate me another unlock.bin with the "wrong" IMEI and correct OEM ID,
so I might be able to unlock it again - and than change the IMEI maybe again for the correct one, and unlock it again with the "correct" unlock.bin.
Click to expand...
Click to collapse
LGs Website is smart enaugh. Nope...
2. Question:
So, if I am allowed to ask in here aswell while I do my research: How to skip my IMEI Issue in the next time? I guess not "restoring" the Mothers-EFS Partition to a Childrens Device should be it - or is the information located in another Partition?
Click to expand...
Click to collapse
Wow. I bricked a second device. Have tried not to Flash Recovery and EFS. Seems like it´s located on Misc or Boot or something like this ...
Damn it.
Anybody knows something more precise?
Thanks