Related
So I did a full wipe and then installed Rodriguezstyle FroYo rom (http://forum.xda-developers.com/showthread.php?t=692609). It was fine but I missed too many CM features and NeXTheme.
I did a wipe, reflashed CM5.0.7.1 and then restored my nandroid (+ext). Now I cannot get the device to boot!
I can get into bootloader and thought I should replace the radio as I know the FroYo one is a problem in non-FroYo roms but while it copies ok, when installing it says FAILED (remote:image update error)
Please please help me. Give me steps to do to get back to a clean CM5.0.7.1 and I can sort the rest out!
Fastboot won't let me flash anything! I am unlocked though!
There's no need to post your question in multiple forums.
Someone will answer when they know how to help.
That said, all I can suggest is maybe trying a different radio image? Or maybe see if you can load up one of the 2.1 ROMs and deal with the radio issue once it's up and running?
Sorry, got a bit desperate
I have tried several radios, the problem is that I cannot flash anything for some reason. I cannot even flash Amon_Ra's recovery to try and get a different rom working
So even booting to fastboot (press and hold trackball during power-on) your computer is unable to connect via fastboot? So "fastboot devices" doesn't return anything?
Just booting normally, what happens? Does it get stuck on the Android bootloader screen or what? Any chance of connecting to it via adb?
I haven't broken my stuff hard yet, so I'm kinda guessing here lol. Trying to help though!
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23
3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
I can't get as far as a recovery image to issue adb commands. When I try to boot normally, the phone vibrates once as the X comes up, then several quick vibrations which seem like some kind of error code.
Also, by way of some extra info in case it helps, the following is displayed on my bootloader:
NEXUSONE PVT SHIP S-ON
HBOOT_0.33.0012
MICROP-0b15
TOUCH PANEL-SYNT0103
Radio-4.02.02.14
Dec 17 2009,13:05:23
Click to expand...
Click to collapse
What is the EXACT command are you typing to flash recovery?
3Shirts said:
I appreciate the help, thanks.
I can get to fastboot and issue fastboot commands (fastboot devices returns the model number (?) as normal). It's just that if I try to fastboot flash recovery I get that "image update error"
Click to expand...
Click to collapse
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......
martin0285 said:
Have you tried this --> http://forum.xda-developers.com/showthread.php?t=614850
It is a sticky..... Anyways, I would also try the official .zip image (PASSIMG.zip) if you can find a thread on that someplace. That loads through fastboot I believe so check it out.....
Also try "Fastboot boot recovery.img" (recovery.img being c:\PATHTOFILE) and see if it will boot into recovery that way......
Click to expand...
Click to collapse
The command I am typing is: fastboot flash recovery recovery.img <- this being the name of the Amon_Ra recovery image file located in the same folder I am in when issuing the command
I have tried that post's instructions but I get "remote: not allowed" when trying to erase userdata and I was getting "remote: image update error" when trying to do any of the flash commands. I say WAS becasue I have just tried sticking the original PASSIMG on sd card and updating that way and, while it gave me partition update errors on boot and system, it has changed something because now when I do the fastboot flash commands I get a different error: "remote: signature verify fail"
I know the files are not corrupt though as I have checked the md5s
EDIT: I also tried doing a fastboot boot to the recovery image but it loads to the X then I get prompted by windows to install a Qualcomm CDMA driver which it can't find?!!
the first case of semi-brick?
like on the G1
JKshowman said:
the first case of semi-brick?
like on the G1
Click to expand...
Click to collapse
Don't say that
Thread Moved.
3Shirts said:
Don't say that
Click to expand...
Click to collapse
no, its just i had a semi-brick problem on the G1 and i solved it quickly enough by reflashing a recovery, but in this case.........
try to see if other flashboot commands work
3Shirts said:
Don't say that
Click to expand...
Click to collapse
Try downloading the recovery image again. It could be corrupt. Also, I am assuming you unlocked your phone first.
No I have confirmed the MD5s on everything I downloaded including the recovery image. Yeah I've been unlocked and rooted from day one.
Does anyone have an hboot image I can try flashing
Well it looks like i'm f***ed then.
I can't adb and can't boot to any kind of terminal so with only fastboot available, and that not allowing me to flash much, I can't fix this
I guess it's off to HTC, see what hey can/will do and if that fails... no more Nexus One
EDIT: Booked it in with HTC for collection tomorrow afternoon (UK time). I'll update again to provide a definitive answer to the question: What is the price for effing up your Nexus One through your own stupidity
The command I am typing is: fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....
martin0285 said:
I realize this, but fastboot BOOT recovery.Img is a different command to just "boot" the image and not "flash" permanently... worth a shot....
Click to expand...
Click to collapse
I have tried that too. It just sits at the X. Doesn't get into recovery
3Shirts said:
I have tried that too. It just sits at the X. Doesn't get into recovery
Click to expand...
Click to collapse
****ty, well good luck with HTC.....
Just to update for anyone interested in the process:
I called HTC on 2nd June and booked collection for the following afternoon.
Picked up by courier (I packed it in original box and jiffy bag with battery but no SD or Sim cards) at 2pm on 3rd June
Received confirmation of arrival with HTC (Milton Keynes as I'm in the UK) at 1.43pm on 4th June
Next step is to wait for a call regarding the repair that can be done and associated cost.
Ok so here's the rundown. I was trying my hand at making the elder scrolls:daedric runes font work for my phone. Got it pretty close, was using fresh type to change some of the preinstalled system fonts. (if you have any idea how i can install a custom font package that would be wonderful as well). but anyway, it asks me to reboot then bam, won't start up.
after reboot after reboot, i decide to say screw it, i pop it into recovery mode and factory reset it. I figure oh well, not much gets lost. turn it back on, still no luck. I give it another go, no luck that time either, i remove both the sim and the SD card and go again, still no money.
At this point i download the full fxz, and RSD lite 5.5 and i boot up into AP fastboot mode and procede to start flashing. Goes well till it hits about step 13 or 14 when then it says fail. I try to restart the phone thinking no big, it probably doesn't need webtop just to boot, now it says
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG OTV (CG: webtop): Invalid SP Data
Invalid CG Version (CG: webtop)
Invalid CG OTV (CG: webtop)
To make matters worse, regardless of what i try to flash ( at this point i'm not even sure if it's flashing) nothing seems to bring it past the AP Fastboot start screen. I've tried the minimal version, the full version with rsd lite. I've tried the standalone fastboot transfer method by moving each image file individually with the ADB daemon. What's infuriating is that each flash says success except for the full FXZ... yet it still never boots past the AP fastboot screen. I might be missing something, i was browsing the forum looking for answers nothing is coming up.
Ran across a few posts about a locked bootloader. Would that have any affect on this? Another few bits of useful info, my battery is full, i have an external charger, i'm running this on a laptop, i have access to a desktop but it's my room mate's and is in his room so i want to disturb him as little as possible, so unless it makes a profound difference i'd like to use my laptop. Any info would be great guys.
Looking forward to some help. I'm about exhausted.
Dhacker29's 1-click restore. Development.
Sent from my DROID BIONIC using xda premium
I've already tried that, and just tried again, finishes, says okay on all steps then when it asks me to root it reboots and goes to the same screen as i mentioned in OP.
bump?............
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Generalkenobi_2 said:
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Click to expand...
Click to collapse
where can you find the full fxz anymore? every link i click on for it says to contact administrator....can only find the minimal one without problem
Generalkenobi_2 said:
Solved it. For future reference, if the problem isn't solved with one click root you'll need to use the full version of the fxz. In addition, using the back of a desktop vs a Laptop makes ALL the difference! USE A DESKTOP.
Click to expand...
Click to collapse
i was able to get my Bionic to the point where i want it..however, whenever the phone powers up or reboots, it ALWAYS goes to the AP Fastboot Screen with the "flash failure" message...i have to turn the phone back off, hold both volume buttons down, press the power button, go into the menu screen and choose "normal POWERUP" and things go along fine.....what can i do to repair my Fastboot function so i don't have to go through this procedure every time. Have tried RSD Lite, but get the same flash failed message
kbatrph said:
i was able to get my Bionic to the point where i want it..however, whenever the phone powers up or reboots, it ALWAYS goes to the AP Fastboot Screen with the "flash failure" message...i have to turn the phone back off, hold both volume buttons down, press the power button, go into the menu screen and choose "normal POWERUP" and things go along fine.....what can i do to repair my Fastboot function so i don't have to go through this procedure every time. Have tried RSD Lite, but get the same flash failed message
Click to expand...
Click to collapse
I need help with this as well my bionic is doing the same thing. Im supposed to be selling it has anyone found a fix for this..?
all you have to do is successfully flash any file and it will stop giving you the flash failure message
IE pick a file flash it using fastboot and voila problem solved. I know this because i ran into this issue when messing with my bootloader research.
Flashing
I went back to stock and applied the update. I tried to root and failed so I tried to flash back to stock. I am stuck entering fastboot like you guys. I can start the phone in recovery but I am looking for a fix. I see that you wrote flash any file to get it to stop. Can you provide some specifics on how you did this and what file you flashed. The one I tried to flash will end in flash failure.
yeah sure:
put the files from the fxz in same folder as adb and fastboot. Reboot into fastboot mode make sure you have drivers for phone.
fastboot flash devtree device_tree.bin
simple and will not loose a thing doing this one.
should clear up your flash failure.
See attached file
denpth said:
yeah sure:
put the files from the fxz in same folder as adb and fastboot. Reboot into fastboot mode make sure you have drivers for phone.
fastboot flash devtree device_tree.bin
simple and will not loose a thing doing this one.
should clear up your flash failure.
Click to expand...
Click to collapse
ii get an error
---------- Post added at 06:42 PM ---------- Previous post was at 06:42 PM ----------
DDRR2 said:
See attached file
Click to expand...
Click to collapse
wont flash...wonder what someones suppose to do with that rar file???
can someone post the fill FXZ and how to flash it? I am hosed at Boot Failure
smilepak said:
can someone post the fill FXZ and how to flash it? I am hosed at Boot Failure
Click to expand...
Click to collapse
just got done fixing this isue myself with the bionic pathsaver method. make sure you read and follow all directions and it will work
DDRR2 said:
See attached file
Click to expand...
Click to collapse
I don't think anybody acknowledged that this works. Thank you to the developer.
I'm having the same issue updating from 886 to 893. The flash fails then boots up to the flash failure screen every time. This is fixed easily with the app above.
DDRR2 said:
See attached file
Click to expand...
Click to collapse
I can't thank you enough for this. When we get to heaven we'll meet Jesus, St. Peter, all the awesome devs out there and you my friend.
thanks that worked like a charm.
driod help
wrong place sorry
Hello anyone know how to remove unlock bootloader warning logo ? Please Help i will be very gratitude for any info
Just download the firmware for your region and extract the file logo_signed, put the device into fastboot mode (press power + vol -) open a console and run the command fastboot flash ulogo logo_signed and reboot your device Hope this helps
Sent from my XT890 using xda app-developers app
You can do it this way
Only ICS and, if the case, maybe Jelly Beam accesed for Homemade
Does not work on Jelly Beam accessed by OTA or RSD Lite
If you mean the caveat that you unlocked bootloader, use the information to a htcmania forum, and as if you can not make a link to there without censor me,
is simple, get files
1. - Fastboot.exe
2. - logo_signed (must be obtained from the firmware, exploring the zip file)
sorry for my bad English
Donwload files
http://db.tt/tak1LsuU
note: logo_signed file is of the firmware: Brasil.en.BR
Procedure
1. - Put the downloaded files in a folder in the root "C" on your pc, (I call this folder Android for example)
2.- Put the phone in fastboot mode (power button and Vol - squeezing them a few seconds until the screen fastboot mode) and connect with USB the phone to pc
3.- Opening a cmd screen, we stand there, I'm in cmd C:\Android\
4. - cheking with command fastboot devices
5. - Performed the command fastboot flash ulogo logo_signed
6. - Conducted after ending command fastboot reboot and that's it
7.- enjoy
Warning: only share what I see written on a forum and I served, so I do not take responsibility for any damage this may cause to your phone
hello
keeps saying somethink about verication lads!!
Does anynone know how to remove this warning from Jelly Bean?
andy_macleod said:
Does anynone know how to remove this warning from Jelly Bean?
Click to expand...
Click to collapse
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
xpc21 said:
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
Click to expand...
Click to collapse
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
andy_macleod said:
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
Click to expand...
Click to collapse
Sorry andy!
This method i´ve tried and worked on Omar-AVelar ROM April 09, the newer ones didnt worked.
I dunno if will work on another.
Bounty
andy_macleod said:
Thanks for you quickly response.
I use stock JB 4.1, may I do your procedure or it just work with cyanogenmod rom?
Click to expand...
Click to collapse
I too am interested in removing the unlocked warning on OTA JB. We should set up a bounty
xd69 said:
I too am interested in removing the unlocked warning on OTA JB. We should set up a bounty
Click to expand...
Click to collapse
The biggest problem of Razr i is the intel architecture x86 not common in mobiles.
xpc21 said:
Sorry andy!
This method i´ve tried and worked on Omar-AVelar ROM April 09, the newer ones didnt worked.
I dunno if will work on another.
Click to expand...
Click to collapse
Do you mean that you think we will never be free from this ugly warning? :crying:
marcospbs said:
Do you mean that you think we will never be free from this ugly warning? :crying:
Click to expand...
Click to collapse
I don't think so. Just for while, soon someone will find a way to disable this "ugly" warning.
xpc21 said:
My friend, download the attatched file and enter fastboot mode, in CMD prompt write the following:
fastboot flash logo logo-CMAK.bmp
fastboot flash ulogo logo-CMAK.bmp
Cheers.
Click to expand...
Click to collapse
It doesn't works on Pi-Lama ROM 0.6
I suggest you don't even try to flash it. You'll brick your phone. I'm currently stuck on Fastboot and can't boot properly, but i've a CWM backup and can't access CWM anymore.
If you're stucked, i suggest you to flash Omar-Avelar boot.img found here.
Speeding up the process
andy_macleod said:
I don't think so. Just for while, soon someone will find a way to disable this "ugly" warning.
Click to expand...
Click to collapse
A high enough bounty would make someone dev it alot faster!
xd69 said:
A high enough bounty would make someone dev it alot faster!
Click to expand...
Click to collapse
For sure. Lets find at least 100 users from razr i and all deposit US$1,00 in a specific paypall account and give the bounty for who find a way to disable this boring warning.
andy_macleod said:
For sure. Lets find at least 100 users from razr i and all deposit US$1,00 in a specific paypall account and give the bounty for who find a way to disable this boring warning.
Click to expand...
Click to collapse
Im willing to input $20 to the cause so that this gets done faster!
Any luck on JB?
Well, this is what I tried just now:
- I pulled 'logo_signed' and 'ulogo_signed' from 'CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip' file, which is the one I had flashed before Omar's ROM.
- I then simple renamed them one with the name of the other (logo became ulogo and viceversa) and tried to flash via 'fastboot flash'
- The error I got was 'Invalid OSID for logo : 2' when attempted to flash 'logo_signed' and 'Invalid OSID for ulogo : 0' for 'ulogo_signed'
- Opened both files using XVI32 and found almost the same header up to hex addr 9A, where there was a 02 on logo file and a 00 on ulogo file
- I edited them, changing the 02 for 00 and viceversa, saved them and tried to flash again, I then get:
At phone's screen:
Fastboot command failed
Getvar max-download size
In cmd screen:
writing 'ulogo'...
Invalid image ulogo
Preflash validation failed
writing 'logo'...
Invalid image logo
Preflash validation failed
At least I got rid of the first error, but have no idea on this second one... any guesses?
.
Hi, what is your command line ? Do you use fastboot ? Rsd lite ?
nick7722 said:
...
- I then simple renamed them one with the name of the other (logo became ulogo and viceversa) and tried to flash via 'fastboot flash'
...
Click to expand...
Click to collapse
I was probably not very clear, I tried flashing them via fastboot, that is 'fastboot flash logo logo_signed' and 'fastboot flash ulogo ulogo_signed'
.
Hi,
My phone boots until the Motorola Logo (M in a red point) but doesn't do anything else. And every 5 minutes, it restarts and stops at the same place. No animation, just stops like that, a rock with a red point ...
My phone is a Motorola Razr I, updated with the last version of android, no unlock, no root, 8months old, just a lambda user, never tried to root or unlock ... I did nothing before it crashed, it was in my pocket, no wifi ... it stopped alone and on restart, the Red Point of Motorola of Death is back ...
I can start the fastboot menu, but only "Shutdown" works. "Normal Powerup", "Recovery", "BP Tool" or "Factory" write the same log :
Booting with [...]
Failed to lock fuse, code = 0xa0b23d
Failed to lock fuse, code = 0xa0b23c
Fuse read failed bank = 4 SEP_RETURN = 0xa0b23c
Fuse read failed bank = 4 SEP_RETURN = 0xa0b23c
Click to expand...
Click to collapse
I searched on Xda or with my friend Google, but nothing works because every indicated solution is used with a working recovery mode ...
Did you already meet this kind of problem ? Is it a hard brick ? Can I use my phone like a doorblocker ?
Thanks for your incoming help
LanceOmelette
PS :sorry for my english ... (swiss-french inside ...)
PPS : need more informations ? It will be a pleasure to give them ... if I know how to find it (android noob inside)
PPPS : I hope, I was clear in my description ...
LanceOmelette said:
Hi,
My phone boots until the Motorola Logo (M in a red point) but doesn't do anything else. And every 5 minutes, it restarts and stops at the same place. No animation, just stops like that, a rock with a red point ...
My phone is a Motorola Razr I, updated with the last version of android, no unlock, no root, 8months old, just a lambda user, never tried to root or unlock ... I did nothing before it crashed, it was in my pocket, no wifi ... it stopped alone and on restart, the Red Point of Motorola of Death is back ...
I can start the fastboot menu, but only "Shutdown" works. "Normal Powerup", "Recovery", "BP Tool" or "Factory" write the same log :
I searched on Xda or with my friend Google, but nothing works because every indicated solution is used with a working recovery mode ...
Did you already meet this kind of problem ? Is it a hard brick ? Can I use my phone like a doorblocker ?
Thanks for your incoming help
LanceOmelette
PS :sorry for my english ... (swiss-french inside ...)
PPS : need more informations ? It will be a pleasure to give them ... if I know how to find it (android noob inside)
PPPS : I hope, I was clear in my description ...
Click to expand...
Click to collapse
I would try reflashing the original firmware using Motorola's RSD Lite Flash Tool
if you are still on warranty send it back to the seller
totex71 said:
I would try reflashing the original firmware using Motorola's RSD Lite Flash Tool
Click to expand...
Click to collapse
Thanks Totex.I tried : the log is :
Getvar max-download-size
Downloading ...
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed
Click to expand...
Click to collapse
and in RSD Lite :
Status : Failed flashing process 1/11 flash gpt "gp_signed" -> phone return FAIL
Click to expand...
Click to collapse
mmmmmh I presume it's bad ... very bad ... :crying:
Thanks ICuaI, I keep a small hope to not use this last advice
LanceOmelette said:
Thanks Totex.I tried : the log is :
and in RSD Lite :
mmmmmh I presume it's bad ... very bad ... :crying:
Thanks ICuaI, I keep a small hope to not use this last advice
Click to expand...
Click to collapse
Is there ICS or JB on it? and did you try to flash ics?. if so, try the latest jelly bean firmware
Which firmware did you try to flash? I think you need this one:
http://sbfdownload.droid-developers.org/smi/CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU.xml.zip
It is retail eu jelly bean
via RazR I & Tapatalk 4
Thanks
but no ...
It didn't work ... now, it failed on step 2
Log on phone :
Getvar max-download-size
Downloading ...
Flashing gpt ...
OEM fb_mode_set
Fastboot command failed
Click to expand...
Click to collapse
which version of RSD-Lite do you use? What did you try?
Come on, tell us a little bit more. With "No it does not work" we cannot help you.
Ok ... sorry ... I will try to do my best :
RSD Lite 6.0 / Windows 8 / I presume Jelly Bean was my last version on my phone because I checked 1 day before for any update.
The informations on fastboot flash mode :
AP Fastboot Flash Mode (secure boot)
20.25 (sha - [...])
IFWI Info: 42.26
eMMC Info: Size 8GB
Barcode: [...]
Battery (Okay): 3.5v (temp 29.0)
Connect USB Data Cable
ROM-Key: Motorola-Key
Modem Status: Secure
Click to expand...
Click to collapse
I tried to flash my phone with the firmwire you gave me
Connect my phone on RSDLite with USB, Select the xml file and start the process. That stopped after few seconds on step 2
All others exemples found on Google to rescue my phone used the recovery mode or an other option given by the fastboot mode : the probem is every option in the fastboot mode (except Power Off) crashes my phone. So I didn't do lot of things finally ...
Can I give you more informations ?
LanceOmelette said:
Ok ... sorry ... I will try to do my best :
RSD Lite 6.0 / Windows 8 / I presume Jelly Bean was my last version on my phone because I checked 1 day before for any update.
The informations on fastboot flash mode :
I tried to flash my phone with the firmwire you gave me
Connect my phone on RSDLite with USB, Select the xml file and start the process. That stopped after few seconds on step 2
All others exemples found on Google to rescue my phone used the recovery mode or an other option given by the fastboot mode : the probem is every option in the fastboot mode (except Power Off) crashes my phone. So I didn't do lot of things finally ...
Can I give you more informations ?
Click to expand...
Click to collapse
Here's your problem. You need RSD 6.14. Other versions are too old to recognize the new Moto phones.
tatazeuz said:
Here's your problem. You need RSD 6.14. Other versions are too old to recognize the new Moto phones.
Click to expand...
Click to collapse
I just tried with RSD 6.1.4 and 6.1.5, same error : OEM fb_mode_set / Fastboot command failed.
I will go to my seller this afternoon and try to use my warrant.
Thanks for your help :-/
LanceOmelette said:
I just tried with RSD 6.1.4 and 6.1.5, same error : OEM fb_mode_set / Fastboot command failed.
I will go to my seller this afternoon and try to use my warrant.
Thanks for your help :-/
Click to expand...
Click to collapse
Go to the xml and delete the command that fails, in this case OEM fb_mode_set
It was an idea I found too but I didn't know the utility of this line and I didn't want to have a brocken version ...
But now my phone is in the hand of my seller ... I can only pray to have it as soon as possible ...
Thank you everybody for your help It was a pleasure to ask you a question The answers were fast and understable for me
I will give you the result of the investigation of my seller (2weeks to 1month) if I don't forget ...
LanceOmelette said:
It was an idea I found too but I didn't know the utility of this line and I didn't want to have a brocken version ...
But now my phone is in the hand of my seller ... I can only pray to have it as soon as possible ...
Thank you everybody for your help It was a pleasure to ask you a question The answers were fast and understable for me
I will give you the result of the investigation of my seller (2weeks to 1month) if I don't forget ...
Click to expand...
Click to collapse
I deleted fb_mode and it all flashes like it should. I think it just sets it up on fastboot or smth like that
Sorry for the delay, I'm on a trip around the world and I just received my phone back from the seller. But like I thought : no discussion, no message to give the reason or the solution. My phone is back, they made a big hardreset.
Thank you, everybody for your help. I learn some new things
Bye
Lance
So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
karlsin said:
So being the hot headed fool that I am, I pretty much just upped and tried to flash a non-stock ROM onto my L90 D415 10c without reading enough about the process. I rooted with towelroot and got into the bootloader, then I thought that simply with an erase command and an update command my phone would just reboot with the new ROM on it, alas this was not true. What I did was
fastboot erase system
fastboot erase boot
After entering "fastboot update cmod.zip" there was a message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
My phone is now stuck in the bootloader, what do I do? Is there any way to restore it's previous settings/memory?
The two "guides" that I followed (pretty much exactly) were first this and then this.
Last thing that seems like it may help is when I type "fastboot continue", my phone ends up with a message saying:
ERROR: Invalid boot image header
If anybody can solve this for me I would be eternally grateful. I've already learned my lesson, and I've got a feeling I'll be coming back to xda. For better reasons I hope. Thanks in Advance
EDIT: I guess I should add that I tried to flash the ROM in fastboot, which now that I think of it, I'm not sure is even possible? I do have my entire terminal history if that helps.
Click to expand...
Click to collapse
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
gdjindal said:
Just follow my KDZ flashing guide and reflash kdz
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
Click to expand...
Click to collapse
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
karlsin said:
The LG Mobile Support Tool doesn't recognize my phone. I followed the directions exactly (plugging the phone in after the first error message), but the same message appears after pressing retry.
Click to expand...
Click to collapse
Power off the phone, pret volume up and insert USB cable . Now follow the guide.
Sent from my LG-D405 using XDA Free mobile app