After doing some reading I found a command to extract the radio file from our phones and crypticsorr0w ended up being our guinea pig and it got him his CKB2 Radio back.
It is now tested and I've inserted it into a cwm file that I took from paulobrien so credit goes to him for that. But it's been tested and it works but you're responsible for what you flash, if something happens don't blame me.
MD5 Sum for this file is: 4e926fdf96a2350c85604b1a00009d
CraneGuy said:
First thing I want to say is this is untested, I did this tonight after my son went to bed and haven't had time to test it. After doing some reading I found a command to extract the radio file from our phones.
update : I put the radio.img file into a zip file and I've been told by zephiK that you need to verify it using md5 hash before using to make sure it doesn't brick your device. If you know how to do that then please go right ahead, in the meantime I'm gonna try to get that done.
In the File properties I get
MD5 Sum : 4e926fdf96a2350c85604b1a00009dc5
So if you don't know how to do that I wouldn't recommend it until someone that does either explains to me how to do it or does it.
Click to expand...
Click to collapse
Nice, what was the command?
Just ran md5 on it, matches what you got.
[email protected]*****:~/Documents/Nexus S/test$ md5sum radio.img
4e926fdf96a2350c85604b1a00009dc5 radio.img
I ran the dd if=/dev/mtd/mtd5 of=/sdcard/radio.img count=12583040
in adb shell and it copied it to the root of my sdcard. Now that that matches it should be safe to flash using fastboot with
fastboot flash radio radio.img command.
you check the md5 hash of your download against the original to test that the download isn't corrupt. on linux, you can do this with:
md5sum filename.zip
on windows, i believe there are many freeware md5 sum checkers you can download to check
yeah I just downloaded a md5 sum checker and checked the md5 hash againts the original and they do match. Plus Kryptic checked it with the #'s I gave him so I'm thinking they're good. If someone that knows more on the subject wants to make sure then you're help is more then welcomed.
About md5 hashes, download hashtab (windows) it makes verifying md5,crc32 etc easy!
Sent from my Nexus S using XDA Premium App
Thanks zephiK, that works a lot better then the other program I was using. Again it just confirmed what I found earlier, they're a match so should be good.
zephiK said:
About md5 hashes, download hashtab (windows) it makes verifying md5,crc32 etc easy!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Sorry new to the Nexus S....
Got a ATT band Nexus S, loaded NScollab and MIUI and neither will keep me connected to the cellular network/3g
I'm assuming its the radio? How do i flash the stock radio you have posted?
beiker44 said:
Sorry new to the Nexus S....
Got a ATT band Nexus S, loaded NScollab and MIUI and neither will keep me connected to the cellular network/3g
I'm assuming its the radio? How do i flash the stock radio you have posted?
Click to expand...
Click to collapse
Did you flash the radio with some other radio? if not, it's the same one your phone came with.
no I just flashed a different rom and I get no service. so need the stock radio I assume
I tried flashing it using fastboot and I get
FAILED (remote: Write Fail)
then I took the file and put it in zip file that contained update script and installed through CWM.
Baseband back to I9020AUCKB2 =>
Thank you again
beiker44 said:
no I just flashed a different rom and I get no service. so need the stock radio I assume
Click to expand...
Click to collapse
The radio will be intact then, no need to flash it.
crypticsorr0w said:
I tried flashing it using fastboot and I get
FAILED (remote: Write Fail)
then I took the file and put it in zip file that contained update script and installed through CWM.
Baseband back to I9020AUCKB2 =>
Thank you again
Click to expand...
Click to collapse
thanks for being the guinea pig!
crypticsorr0w said:
I tried flashing it using fastboot and I get
FAILED (remote: Write Fail)
then I took the file and put it in zip file that contained update script and installed through CWM.
Baseband back to I9020AUCKB2 =>
Thank you again
Click to expand...
Click to collapse
Glad to hear it worked! Now I can edit to say it's tested. So you say it didn't work typing in "fastboot flash radio radio.img" in your android sdk tool folder using adb with your phone in bootloader mode? Just making sure cause it should've worked. oh well just need to make it into a cmw file then and it should be good.
beiker44 said:
no I just flashed a different rom and I get no service. so need the stock radio I assume
Click to expand...
Click to collapse
You get no Service or no 3G?
Glad to hear it worked! Now I can edit to say it's tested. So you say it didn't work typing in "fastboot flash radio radio.img" in your android sdk tool folder using adb with your phone in bootloader mode? Just making sure cause it should've worked. oh well just need to make it into a cmw file then and it should be good.
Click to expand...
Click to collapse
Below are screenshots when trying it in both methods
PS: I used the script from paulobrien XXKB3 zip file http://forum.xda-developers.com/newreply.php?do=postreply&t=1044261
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
crypticsorr0w said:
Below are screenshots when trying it in both methods
PS: I used the script from paulobrien XXKB3 zip file http://forum.xda-developers.com/newreply.php?do=postreply&t=1044261
Click to expand...
Click to collapse
Thanks crypticsorrow, after I read about your problem with fastboot I had to try it and I got the same error so I did the exact same thing you did and by the time I had it posted you said you got it from paulobrien . I tried this cwm file on mine and it said it worked, so it flashed it over my KB2 baseband but still should be good.
Glad we can now flash without worrying too much about losing our baseband.
I tried this cwm file on mine and it said it worked, so it flashed it over my KB2 baseband but still should be good.
Click to expand...
Click to collapse
I am abit confused by what you mean here. I used your radio.img file, i just placed it inside XXKB3-GRI54-radio-nexuss-unsigned.zip from paulobrien post instead of his radio.img. If that is what you did you should not lose your KB2 baseband.
crypticsorr0w said:
I am abit confused by what you mean here. I used your radio.img file, i just placed it inside XXKB3-GRI54-radio-nexuss-unsigned.zip from paulobrien post instead of his radio.img. If that is what you did you should not lose your KB2 baseband.
Click to expand...
Click to collapse
I did the exact same thing you did except I renamed the file to show the correct baseband, I just wanted to see if I'd get any errors from doing it that way and I didn't so shouldn't be a problem.
Ah sorry for misunderstanding that..
Mind if I ask how did you find out which directory has the radio in /dev?
I would like to learn more about dumping to images
Related
Any body having problems updating maunauly after flashing cyanogens multitouch. Nexus cnat verify package. Can anyone help?
If the package can't be verified it's probably bad...or a corrupted download. Try downloading it again.
I tried downloading file three time and still get the same thing. Does it have to do anything with flashing cyanogens multitouch? should I wait for OTA update?
I too am having this issue. I am more than willing to donate to his hacking cause if I can just find a way to get this update. I am no opposed to flashing EVERYTHING back to factory. Please would someone look into this.
It's working now
artvandelay300 said:
I too am having this issue. I am more than willing to donate to his hacking cause if I can just find a way to get this update. I am no opposed to flashing EVERYTHING back to factory. Please would someone look into this.
Click to expand...
Click to collapse
I was able to process the update using a guide i found androidcentral . com
I am too new of a member to post links I guess. If you need this link feel free to let me know. Loving the new update
I'm having the same exact problem. Rooted my n1 to install cyanogen's multitouch and now when i try to manually install the OTA update it fails. I'm desperate for help >__< anyone have any tips?
Ok, so here's what I've learned over the last 18 hours.
If your phone is rooted, custom rom OR stock, you can't install the official update package, either over the air, or manually.
You CAN, however, install the patched version of it that modaco released here:
http://forum.xda-developers.com/showthread.php?t=627411
You'll need, at minimum, his 'main update,' and his 'radio update.
You'll also need his NEW VERSION of superboot, if you want to re-root your phone. Installing the updates breaks root, so you'll need this.
DO NOT use the old superboot that you previously used. It broke my Wi-Fi. Get the new one.
Additionally, you'll have to switch from the stock recovery program to Amon-Ra's recovery, available here:
http://forum.xda-developers.com/showthread.php?t=611829
The stock recovery program can only install official updates, and on a rooted phone, that doesn't seem to work. So use Amon-Ra.
So, to review here's the steps in the order you'll need to do them:
1. Install Amon-Ra Recovery 1.5.3
2. Install modaco's main update
3. Install modaco's radio update
4. Use fastboot to flash modaco's new superboot.img to re-root your phone.
Done!
Ok so assuming i follow that tutorial and break my root access, i'd be able install future OTA updates without having to go through all this again correct?
The only reason we can't install it manually now is because we're rooted so it would make sense to say that removing root access would let us perform future updates legit without having to find patches right?
I'm new to android and i honestly don't even need root privileges, i only wanted multitouch.
Well, to my understanding, no, you won't be able to install stock OTA updates, because your rom (your OS), is no longer stock, so stock updates will fail verification, like they did with this one.
I think you can probably restore OTA ability by reflashing your phone with the stock rom, thereby restoring it to the stock state. There's a very detailed tutorial here, with links to a stock image:
http://forum.xda-developers.com/showthread.php?t=614850
Also, here's a link that's stickied in the developer's forum for stock recovery options from modaco. Slightly less detailed, but it looks simpler to me:
http://forum.xda-developers.com/showthread.php?t=619801
I'm pretty sure that being rooted at all breaks OTA support, and having anything in the OS non-stock also breaks OTA support (ie the early MT browser). I could be wrong on that, but I think that's the case.
Crap. I wan't to try installing the stock rom but i'm looking at the directions and i can't follow them. I'm guessing all the things in bold are commands i have to run somewhere but i don't know where.
Yeah, it's a bit confusing, and a lot to get your head around.
You mean the fastboot commands?
You used fastboot when you rooted, right? To flash the superboot.img.
You have to plug your phone into your computer and reboot while holding down the trackball to get the fastboot screen (the white screen).
Then you put the stock images in the same directory as fastboot (which you should still have from when you rooted your phone with superboot) and flash them, using the commands from the tutorial page. (You run them from the command prompt or terminal, depending on what OS your computer has)
tonyx3 said:
So, to review here's the steps in the order you'll need to do them:
1. Install Amon-Ra Recovery 1.5.3
2. Install modaco's main update
3. Install modaco's radio update
4. Use fastboot to flash modaco's new superboot.img to re-root your phone.
Done!
Click to expand...
Click to collapse
Thanks Tony I was also a nub and trying to find the proper way to de-root my phone this worked 100%!
Deetz said:
Thanks Tony I was also a nub and trying to find the proper way to de-root my phone this worked 100%!
Click to expand...
Click to collapse
De-root? So you didn't re-root with the new superboot?
Also, you do know that your phone isn't stock now, right? And that future OTA updates will probably not work without similar steps?
If you followed those instructions, you now have the update, but it's a modded version of it, designed for non-stock roms.
Glad it worked, though!
tonyx3 said:
Yeah, it's a bit confusing, and a lot to get your head around.
You mean the fastboot commands?
You used fastboot when you rooted, right? To flash the superboot.img.
You have to plug your phone into your computer and reboot while holding down the trackball to get the fastboot screen (the white screen).
Then you put the stock images in the same directory as fastboot (which you should still have from when you rooted your phone with superboot) and flash them, using the commands from the tutorial page. (You run them from the command prompt or terminal, depending on what OS your computer has)
Click to expand...
Click to collapse
The tutorial i used to root my phone required me to download superboot and put the folder in my C: drive. The folder is called superboot but when i was running commands on the command prompt some of them said fastboot, so is superboot the same thing as fastboot? This is what that folder looks like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's what i THINK i have to do.
Download the stock image, extract all the files and put it into the superboot folder i have on my C: drive. Then open up a command prompt and type in:
Code:
cd\
cd\superboot
adb reboot bootloader
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash system system.img
All while my n1 is plugged in while booted normally but with debugging enabled.
Is this correct or am i missing something?
Fastboot and superboot aren't the same thing.
Fastboot is the bootmode on your phone when you hold the trackball down while powering on. The one with the white screen and androids on skateboards. Fastboot allows you to connect via usb and the command prompt to run some commands on the phone, via your computer, such as flashing the img's on.
Superboot is the name of the img file you flashed (using fastboot), which alters the boot up settings on the phone, giving you root priveleges.
As for your list of commands, I think it looks right. Just do all the steps from the tutorial for restoring stock.
Yes, you start with the phone booted normally, but with debugging enabled. But when you use the adb reboot bootloader command, it will reboot into fastboot mode. You could skip that step and just turn your phone on while holding the trackball down.
Good luck!
And let us know how it goes, eh?
Oh ok cool, i think i get it now.
One last thing before i give it a try though, i was looking at step 11 but a file they want me to flash isn't in my superboot folder, even when i dump the stock firmware files in there. Do i have to get the file "system.img" from somewhere first and put it in the superboot folder or is it auto-generated some how?
Code:
Step 11. fastboot flash system system.img
-edit-
also, this is what my superboot folder looks like WITH the stock firmware files dumped into it:
The boxed files are from the unzipped firmware. Did i place them correctly?
Oh, I see.
The tutorial page has two links to stock roms.
But they seem to be in slightly different formats. The first one is hosted on rapidshare, and the second on modaco, right? So you downloaded
"22607-ERD79-update-nexusone-stock-signed.zip"???
That one has it in a different format from the instructions. Either download the one on rapidshare, or go here and get the "Image Format Download" :
http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/300414/18-jan-22607-erd79-stock-rom-for-nexus-one-images-update-zip-online-kitchen-optional-root-insecure/
(note: i've downloaded the one on rapidshare, but not the one on the modaco page I just linked, so I can't verify that they're identical, although they appear to be. I'm downloading the modaco one now, to check the md5sum)
Edit: I downloaded the modaco image in the link, and it is indeed exactly the same as the one hosted on rapidshare in the tutorial (the md5sums match)
Oh ok, ill try grabbing it now then.
I did a checksum for MoDoCos and got a mismatch. Zipped i get:
Code:
5e17b0351024c8fb1a2020f1fd55210e
and non-zipped is:
Code:
e4cf141242e1a362f136a8afd841e0f3
Either way, the rapidfire one is downloading so ill see if that has what i need
-edit-
Cool, the rapidfire md5sum matches up and has my missing file
PhantomRampage said:
Oh ok, ill try grabbing it now then.
I did a checksum for MoDoCos and got a mismatch. Zipped i get:
Code:
5e17b0351024c8fb1a2020f1fd55210e
and non-zipped is:
Code:
e4cf141242e1a362f136a8afd841e0f3
Either way, the rapidfire one is downloading so ill see if that has what i need
Click to expand...
Click to collapse
Right, the checksums won't match, cause the data is different zipped and unzipped. The math that it does on the data wont yield the same result. But the zipped one you posted matches mine. And the other download should match the md5sum posted in the tutorial.
Ok so everything went fine, i now have a non-rooted nexus one with an unlocked bootloader.
Unfortunately, i still cant manually install the OTA update I get:
Code:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying current system...
assert failed: apply_patch_check(MTD:boot:20930
56:1d155a5be2f8cc6d7cef733f87f3bce97be2c3bd:2101
248:e7f20e513e5bd5c30e20670e992092296ee731a0")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
So what are my options now? Oh and thanks tony, i really appreciate your help
Ok guys I managed to identify a file in /root/cache that was downloaded when downloading the firmware straight from the tablet. The file is named "dlpkgfile" and its about 230Mbs, hopefully this can help some ppl. I don't recommend you use this file if you aren't a dev, since I don't know if it can do something bad to your tablet. I have no knowledge of this type of thing, just trying to give a helping hand....
Anyways I uploaded it to my dropbox, so please only devs download it for now I don't want to get a lot of traffic in my dropbox and be shutdown or something lol
My dropbox public link was taken down due to excessive traffic, there are a couple of mirrors around the thread.
I hope someone can verify this soon. I would love to be able to update since my Tablet failed the update :/
Isn't there a way to DL into my own dropbox from yours? That should (at least in my mind) not count as downloads right?
Either way I'm waiting for someone much braver than I to grab this and explain how to flash it. By that time I'm sure it'll be rehosted somewhere else
Just wait till it gets posted on Asus's site, that's what I'll be doing...
Sent from my Transformer Pad TF300T using xda app-developers app
Pretty sure you can just rename it to *.zip and flash it through the recovery.
All the files from the folder patch need to lose their .p suffix and go in /system before you flash it.
need the doctors around
sparky28000 said:
Pretty sure you can just rename it to *.zip and flash it through the recovery.
All the files from the folder patch need to lose their .p suffix and go in /system before you flash it.
Click to expand...
Click to collapse
did that and it did open in 7zip
kindrudekid said:
did that and it did open in 7zip
Click to expand...
Click to collapse
You flashed it?
Sent from my ADR6425LVW using Tapatalk 2
aostl said:
You flashed it?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
It looks like it's the update file
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just wondering if this method: http://forum.xda-developers.com/showthread.php?t=1668173 would still work to root.
Looks like an update.zip package with a blob inside. Should be recovery flashable...
Still recommend flashing over the latest ICS US base.
it does not flash you get status error 7
Probably just a buildprop error. What ROM did you try flashing from?
tysj said:
Probably just a buildprop error. What ROM did you try flashing from?
Click to expand...
Click to collapse
stock
This should help ppl force the update coming from US firmware I think: http://forum.xda-developers.com/showthread.php?t=1803090
You need almost an intact /system to flash this.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.3.30-20120604:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.9-20120809:user/release-keys");
assert(getprop("ro.product.device") == "EeePad" ||
getprop("ro.build.product") == "EeePad");
Click to expand...
Click to collapse
This is a diff patch update.zip.
Whatever you do DO NOT flash the blob from the dlpkgfile on a WW tf300. This will leave you with an us bootloader and for some reason I can't seem boot into the recovery after flashing. And I cannot flash any blob because it says the blob has an invalid signature.
Pretty much stuck here right now... I think I'll have to wait until jb is on the asus website.
How did you flash the blob alone?
Which firmware did you come from?
xaueious said:
How did you flash the blob alone?
Which firmware did you come from?
Click to expand...
Click to collapse
Flashed the blob via fastboot (fastboot -i 0x0B05 flash boot blob) I didn't think it would flash a whole new bootloader. And I came from WW 9.4.3.30. I can't reflash the old bootloader because fastboot doesn't want to actually flash it even though it says everything went okay.
sparky28000 said:
Flashed the blob via fastboot I didn't think it would flash a whole new bootloader. And I came from WW 9.4.3.30.
Click to expand...
Click to collapse
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Quick glance at update-script seems to indicate that it shouldn't remove root from a rooted device running 9.4.3.30, but I'm not sure what's in the blob.
xaueious said:
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Click to expand...
Click to collapse
I hope so.
---------- Post added at 08:45 PM ---------- Previous post was at 08:43 PM ----------
xaueious said:
Well I think I'll be fine. I converted my WW to US 9.4.3.30 and am now flashing the dlpkgfile using the method I linked to.
I am not bootloader unlocked.
Quick glance at update-script seems to indicate that it shouldn't remove root from a rooted device running 9.4.3.30, but I'm not sure what's in the blob.
Click to expand...
Click to collapse
The blob contains a boot.img, recovery.img and bootloader.img.
I already have an US bootloader. I think converting from WW to US did that.
The update.zip does not change /system/bin/su
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No wait times
No subscriptions
No BS
Ace
Many thanks to the ORIGINAL guy, football. He carried this community far with all his releases
Also thanks to tmartin for helping me stay on top of all the RUUs
Fixed link
jmz said:
Fixed link
Click to expand...
Click to collapse
thank you very much
TY
AndroidFileHost said:
No wait times
No subscriptions
No BS
Ace
Many thanks to the ORIGINAL guy, football. He carried this community far with all his releases
Also thanks to tmartin for helping me stay on top of all the RUUs
Click to expand...
Click to collapse
Thank you very much. :good:
I tried to flash this rom.
The result, fixed black screen with backlight.
Here are the steps that I followed.
With ClockworkMod Recovery v5.8.1.5
-wipe data/factory reset
-wipe cache partition
-Wipe Dalvik Cache
-Wipe Battery Stats
-Install zip from sdcard
-choose zip from sdcard
I followed the procedure with a sd card blank, with inside only the zip file of the rom.
I've already used for other updates this sd card.
After the reset, I waited +/- 15 minutes, around the time the screen remained black.
Does anyone know what problem might be?
I need this update to be able to do the s-off.
At the moment I installed CM11 but the GPS does not work, for this reason, I want to be able to try different radio make the s-off
renedrive said:
I tried to flash this rom.
The result, fixed black screen with backlight.
Here are the steps that I followed.
With ClockworkMod Recovery v5.8.1.5
-wipe data/factory reset
-wipe cache partition
-Wipe Dalvik Cache
-Wipe Battery Stats
-Install zip from sdcard
-choose zip from sdcard
I followed the procedure with a sd card blank, with inside only the zip file of the rom.
I've already used for other updates this sd card.
After the reset, I waited +/- 15 minutes, around the time the screen remained black.
Does anyone know what problem might be?
I need this update to be able to do the s-off.
At the moment I installed CM11 but the GPS does not work, for this reason, I want to be able to try different radio make the s-off
Click to expand...
Click to collapse
flashed original boot.img from that rom after installing the rom?
Mpidemie said:
flashed original boot.img from that rom after installing the rom?
Click to expand...
Click to collapse
I tried.
Some other times had worked.
In recent times gives me error.
Code:
sending 'boot' (3034 KB)...
OKAY [ 0.531s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.015s
Also gives me the same error with other boot.img from other ROM, if I try to flash it.
I do not know why.
Thanks men
Enviado desde mi LG-D802 mediante Tapatalk
I have HTC Desire HD A9191..Android Version 2.3.5 and HTC Sense Version 3.0...Baseband 12.65.60.29U_26.14.04.28_M
Software Version 3.13.61.5 ...HBoot -2.00.0029....CID NRANG001. It is from Israel Orange and sim locked.
So, My phone is in semi boot loop. So I tried lot of places for the official Version of Rom. If you can help me please. I don't have gold card and I cant boot my phone.
thank's :good:
richie16171 said:
I have HTC Desire HD A9191..Android Version 2.3.5 and HTC Sense Version 3.0...Baseband 12.65.60.29U_26.14.04.28_M
Software Version 3.13.61.5 ...HBoot -2.00.0029....CID NRANG001. It is from Israel Orange and sim locked.
So, My phone is in semi boot loop. So I tried lot of places for the official Version of Rom. If you can help me please. I don't have gold card and I cant boot my phone.
Click to expand...
Click to collapse
First Try flashing the boot.ini
if it doesnt work you may need to flash the ROM again.
roheed said:
First Try flashing the boot.ini
if it doesnt work you may need to flash the ROM again.
Click to expand...
Click to collapse
Thank you for your advice.. I am seeking the original Orange Israel Rom. I cannot flash any other Rom. It just says fail.. download correct rom and try again..I tried already 3 RUU from different versions. But no where I am getting the Orange Israel RUU.
And flashing the boot.ini ... can you please explain me how to flash and where to obtain boot.ini file please...thank you
richie16171 said:
Thank you for your advice.. I am seeking the original Orange Israel Rom. I cannot flash any other Rom. It just says fail.. download correct rom and try again..I tried already 3 RUU from different versions. But no where I am getting the Orange Israel RUU.
And flashing the boot.ini ... can you please explain me how to flash and where to obtain boot.ini file please...thank you
Click to expand...
Click to collapse
regarding Orange Israel ROM, you can google.
once you've found the ROM, the boot.ini will be inside the zip file. you just need to copy it to the android tool folder (that you may be using to connect via ADB through command prompt).
run: flashboot boot boot.ini
roheed said:
regarding Orange Israel ROM, you can google.
once you've found the ROM, the boot.ini will be inside the zip file. you just need to copy it to the android tool folder (that you may be using to connect via ADB through command prompt).
run: flashboot boot boot.ini
Click to expand...
Click to collapse
Thank you so much ...I understood the process., If I am not mistaken.. the RUU files are exicutive files. Do you think we can extract them? And my biggest problem is, I am not finding anywhere the said Rom. If you find one please let me know.
AndroidFileHost said:
No wait times
No subscriptions
No BS
Ace
Many thanks to the ORIGINAL guy, football. He carried this community far with all his releases
Also thanks to tmartin for helping me stay on top of all the RUUs
Click to expand...
Click to collapse
wow thank you
thanks
nice post but i dont use stock roms anymore.
teşekküler ok very good thank you
I'm using TWRP 2.7.1.0 on a Droid Razr M Kitkat. Whenever I try to flash an xt907 rom it gives me the error:
This package is for xt925,xt926, ..... and on, and doesn't flash. Here's how I've done the process:
Revert to stock KitKat with the VZW and RSD Lite tool
Install towel root and root my phone
Install motopacalypse and unlocked my phone (it's already unlocked so I've ran that once just to unlock it)
Reboot into fastboot and flash TWRP for Razr M
Then reboot to recovery and try to flash an xt907 rom
I've tried B62-Comotion, I've tried an AOKP PURE rom and various others, but it gives me that same error everytime.
Any help on what to do?
I believe the Roms your trying to flash has asserts in the updater-script and is built for the xt925/926 where are you getting the Roms from? Are you sure that they are compatible with the M xt907…? As the asserts in the updater-script are to prevent people from flashing the ROM on a device its not meant for so you won't brick your device...
Sent from my XT907 using XDA Premium 4 mobile app
Like EZKnives said, it looks like you're trying to flash ROMs that aren't compatible.
Sent from your Mom's M8
yes, make sure it is specifically for the xt907 or is a compatible msm8960 build on the KB bootloader.
[Q] What I'm doing wrong??
Following my previous question and remembering the great performance of MIUIandroid V4 for GT-i5500, I want to install MIUIv5 4.2.7 ROM for our Smartphone... Because I'm coming from Samsung GT-i5500 and the only thing we need to use is ODIN, I'm searching how to flash ANY rom on our device and I didn't find any information/tutorial/guide/how-to; only the CM guide, what is very awful.
I've finally reached to unlock the bootloader and I verified what I have "UNLOCKED Code 3" FastBoot. I'm in the point where I need to install an recovery.
After almost 30 minutes searching, I found the tool "Flashify". I've the CWM-Based Recovery img on my device and I want to install it (I really don't understand the instructions what CyanogenMod gave me).
Flash > Recovery image > Choose a file > recovery.clo...-xt907.img (I'm reading from the device).
It ask me if I want to flash the recovery. Answer: Yup!
After reboot: The image "Warning Bootloader Unlocked", and... ... ... ... nothing. Just nothing. It lasts A LOT for come out of this screen (that only happened when I installed the Recovery), reboots without any order, shows again that ugly screen and turns on the OS. When I turn off and hold Vol Down + Power buttons, NOTHING.
Can I know what I'm doing wrong??
What's your system version...? Sounds like you flashed the incorrect recovery
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
What's your system version...? Sounds like you flashed the incorrect recovery
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
If you're talking with me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope this helps. Also, I'm downloading the Recovery what is at the page of rommanager. Flashify didn't found ANY recovery for my smartphone
The name of the recovery (I think) explains for itself:
recovery-clockwork-6.0.4.4-xt907.img
Click to expand...
Click to collapse
EDIT:
A think what happened recently: When I'm in the OS, the device didn't recognize the commands. meanwhile it says "attatched", when I send any command it says <waiting for device>.
When I reload the fastboot via Power Menu, it recognizes ALL the commands. How I know? I changed the ugly Unlocked BootLoader image with the original M in a red circle
Pedreo1997 said:
If you're talking with me:
I hope this helps. Also, I'm downloading the Recovery what is at the page of rommanager. Flashify didn't found ANY recovery for my smartphone
The name of the recovery (I think) explains for itself:
EDIT:
A think what happened recently: When I'm in the OS, the device didn't recognize the commands. meanwhile it says "attatched", when I send any command it says <waiting for device>.
When I reload the fastboot via Power Menu, it recognizes ALL the commands. How I know? I changed the ugly Unlocked BootLoader image with the original M in a red circle
Click to expand...
Click to collapse
OK... I can't see that image bit the name looks right here are the recoveries... And here are some boot logos..
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
OK... I can't see that image bit the name looks right here are the recoveries... And here are some boot logos..
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
I'm curious about why you can't see the image. I was hoping, instead, what you were going to confront me about the fact what it's in spanish (I know it's obvious what I'm not from an English-talking country)... If you want, here is the text what is in the image:
System Version: 183.46.10.XT907.Verizon.en.US
Model number: DROID RAZR M
Android version: 4.4.2
Baseband version: SM_BP_101031.042.32.86P
Kernel Version:
3.4.42-g5170b6b
[email protected] #1
Fri May 2 00:30:06 PDT 2014
Comp. number: KDA20.62-10.1
Comp. Date: Fri May 2 00:20:25 PDT 2014
Click to expand...
Click to collapse
And about the boot logo, it was only an extra I was telling: The fastboot is working because I reached to edit the ugly Warning Image, that's it
For end: Are you telling what for our device the recovery what is in the official page of CyanogenMod isn't the right one? However, I'm going to try with the first link. Thanks
@pedreo... That's what I was checking for... I don't use CWM but the one for the M on 4.4.2 is CWM6049-RAZR-HD_M-KITKAT.img which is in the link previously post... I hear a lot of people have issues with CWM... TWRP seems to work best.... Its just best to pull it from the posted link to ensure you have the proper version... RikRong knows more about it(well pretty much everything android) then me ..
We cannot teach people anything; we can only help them discover it within themselves.
Pedreo1997 said:
I'm curious about why you can't see the image. I was hoping, instead, what you were going to confront me about the fact what it's in spanish (I know it's obvious what I'm not from an English-talking country)... If you want, here is the text what is in the image:
And about the boot logo, it was only an extra I was telling: The fastboot is working because I reached to edit the ugly Warning Image, that's it
For end: Are you telling what for our device the recovery what is in the official page of CyanogenMod isn't the right one? However, I'm going to try with the first link. Thanks
Click to expand...
Click to collapse
Yeah, neither CWM or TWRP are official for this phone, so they won't show up on the team's websites. The link that EzKnives posted has the recoveries you want.
Sent from your Mom's M8
Philz Recovery
If you are intent on using a CWM type of recovery for our Razr M, the current version of philz recovery is working on our devices, thanks to the unified moto_msm8960.
Here is the link:
https: //goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960/
Being that I haven't posted before on the site, (been lurking for years), I am not able to post the link as clickable, so copy and paste and remove spaces. Please keep in mind that this will only work on the KK Bootloader, but in my tests, it works just fine. I do prefer the TWRP 2.7.1.0 overall, but philz is not bad.
Hope this helps.
This is guide is how l am solved this error on my HTC Desire 816 Dual CID HTC_622 but l think this gonna work for most users with unlocked bootloader
IMPORTANT NOTICE:EVERYTHING I WROTE HERE I DONE ON MY PHONE.I AM NOT GONNA BE RESPONSIBLE IF YOUR PHONE GET BRICKED OR SOMETHING LIKE THAT.
1: Make sure you have Lollipop update available for your phone
2: Download update to your phone,update will be placed in Download folder in your phone internal storage.
3: Extract OTA update file on your pc.Open it with WinRar or some other zip\rar extract program.Find file firmware.zip inside and extract it to your pc.How again open file firmware.zip and inside look for recovery.img file and extract it too to your pc
4: How you need to flash extracted recovery.img file via fastboot.Boot phone in bootloader mode and flash new recovery.
5: Relock your bootloader.
6:Reboot your phone now.Again download update for your phone,and try to flash OTA update again:fingers-crossed:
HTC A5_DUG Stock Recovery Mega link: https://mega.co.nz/#!aBkGyRLK!LcRMMPTF7hhaUTUNxJBZ4FJbF3QMhLtWswW1Vxvn2YI
Thank you for your useful tips.
I will try and feedback soon.
Thanks a lot! It worked for me
Note that you don't have to relock the bootloader, it worked with it unlocked.
Also I heard it is recommended to wipe dalvik cache and cache partition after update.
There are two rules about which recovery you can use:
1) You must use the recovery for your exact model! It must also be from the same region! (recovery for A5_DUG Europe won't work for you if you have A5_DUG Asia_HK, or A5_UL any, etc.)
2) You must use the recovery from the version you are currently at OR the one you are updating to! (the recovery from 1.56.708.2 won't work if you are updating from 1.57.708.1 to 2.34.708.1, etc.)
OronDF343 said:
--snip--
Click to expand...
Click to collapse
If anyone has Desire 816 dual sim A5_DUG Asia_HK you can use the recovery image that I extracted. (Attached in two parts)
OronDF343 said:
Thanks a lot! It worked for me
Note that you don't have to relock the bootloader, it worked with it unlocked.
Also I heard it is recommended to wipe dalvik cache and cache partition after update.
There are two rules about which recovery you can use:
1) You must use the recovery for your exact model! It must also be from the same region! (recovery for A5_DUG Europe won't work for you if you have A5_DUG Asia_HK, or A5_UL any, etc.)
2) You must use the recovery from the version you are currently at OR the one you are updating to! (the recovery from 1.56.708.2 won't work if you are updating from 1.57.708.1 to 2.34.708.1, etc.)
Click to expand...
Click to collapse
l know that you dont have to relock bootloader but l want to lock it just to be sure:laugh:
Aimbot91 said:
l know that you dont have to relock bootloader but l want to lock it just to be sure:laugh:
Click to expand...
Click to collapse
I am trying this way so i'll tell you if it works. I hope finally this will work
ctnerdem said:
I am trying this way so i'll tell you if it works. I hope finally this will work
Click to expand...
Click to collapse
Ok:fingers-crossed:
Aimbot91 said:
Ok:fingers-crossed:
Click to expand...
Click to collapse
it gives me this error every time i try.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ctnerdem said:
it gives me this error every time i try.
Click to expand...
Click to collapse
Are you used OTA for your deviceMaybe your OTA zip file get corupted?
Yes I used ota for update but I don't understand this error what it means
Aimbot91 said:
This is guide is how l am solved this error on my HTC Desire 816 Dual CID HTC_622 but l think this gonna work for most users with unlocked bootloader
IMPORTANT NOTICE:EVERYTHING I WROTE HERE I DONE ON MY PHONE.I AM NOT GONNA BE RESPONSIBLE IF YOUR PHONE GET BRICKED OR SOMETHING LIKE THAT.
1: Make sure you have Lollipop update available for your phone
2: Download update to your phone,update will be placed in Download folder in your phone internal storage.
3: Extract OTA update file on your pc.Open it with WinRar or some other zip\rar extract program.Find file firmware.zip inside and extract it to your pc.How again open file firmware.zip and inside look for recovery.img file and extract it too to your pc
4: How you need to flash extracted recovery.img file via fastboot.Boot phone in bootloader mode and flash new recovery.
5: Relock your bootloader.
6:Reboot your phone now.Again download update for your phone,and try to flash OTA update again:fingers-crossed:
HTC A5_DUG Stock Recovery Mega link: https://mega.co.nz/#!aBkGyRLK!LcRMMPTF7hhaUTUNxJBZ4FJbF3QMhLtWswW1Vxvn2YI
Click to expand...
Click to collapse
How to Flash the file exactly ??
OronDF343 said:
Thanks a lot! It worked for me
Note that you don't have to relock the bootloader, it worked with it unlocked.
Also I heard it is recommended to wipe dalvik cache and cache partition after update.
There are two rules about which recovery you can use:
1) You must use the recovery for your exact model! It must also be from the same region! (recovery for A5_DUG Europe won't work for you if you have A5_DUG Asia_HK, or A5_UL any, etc.)
2) You must use the recovery from the version you are currently at OR the one you are updating to! (the recovery from 1.56.708.2 won't work if you are updating from 1.57.708.1 to 2.34.708.1, etc.)
Click to expand...
Click to collapse
Thanks for the info. But
How to know which recovery do i have?
OronDF343 said:
If anyone has Desire 816 dual sim A5_DUG Asia_HK you can use the recovery image that I extracted. (Attached in two parts)
Click to expand...
Click to collapse
Worked a charm and saved me a lot of trouble. Thank you very much.
/M
ctnerdem said:
it gives me this error every time i try.
Click to expand...
Click to collapse
I got the same error on my A5-UL when updating the OTA. Tried installing Google Books, but the same error happens.
!!~spearhead~!! said:
I got the same error on my A5-UL when updating the OTA. Tried installing Google Books, but the same error happens.
Click to expand...
Click to collapse
I had a very similar error.
my guess is, because my phone is unlocked and modified using Link2SD and Xposed, there have been changes to the system. so It might be a good idea to flash an untouched 4.4.42 nandroid before trying to update.
That's what I did and I could update without a problem
Stock recovery ?
OronDF343 said:
If anyyone has Desire 816 dual sim A5_DUG Asia_HK you can use the recovery image that I extracted. (Attached in two parts)
Click to expand...
Click to collapse
hello ...........
I'm stuck on STOCK RECOVERY
After extracting OTA file and all that ........ I too got recovery.img file
but i dont understand how to use that file to solve the red triangle issue\
please help me !!
Chary Harish said:
hello ...........
I'm stuck on STOCK RECOVERY
After extracting OTA file and all that ........ I too got recovery.img file
but i dont understand how to use that file to solve the red triangle issue\
please help me !!
Click to expand...
Click to collapse
you copy that recovery.img file to the folder where you keep your ADB/Fastboot files. then you reboot to bootloader and put your device in fastboot mode. then open a command prompt in your fastboot folder on your computer and type:
Code:
fastboot flash recovery recovery.img
unexpected contents
Stucked passed 3 nights trying ,I unrooted my phone than installed custom recovery and tried but it says system/apps/... Has unexpected contents status 7 I don't have nandroid backup can anyone help me my device a5 dug europe
Ali_5don said:
Stucked passed 3 nights trying ,I unrooted my phone than installed custom recovery and tried but it says system/apps/... Has unexpected contents status 7 I don't have nandroid backup can anyone help me my device a5 dug europe
Click to expand...
Click to collapse
the error is because you had modified your old Rom(i,e, definitely uninstalled things from system) so it fails system check. you can find clean unchanged nandroid backups of 1.58.401 on XDA
:good:
seekfind said:
the error is because you had modified your old Rom(i,e, definitely uninstalled things from system) so it fails system check. you can find clean unchanged nandroid backups of 1.58.401 on XDA
Click to expand...
Click to collapse
I tried but can't find a nandroid backup if u have a link than can u post bro I am browsing [http://forum.xda-developers.com/desi...l-sim-t3030958]. Have a look at it! http://forum.xda-developers.com/desire-816/general/fresh-htc-desire-816-a5dug-dual-sim-t3030958 will this work but its cid and myn is europ