I have a specific problem .. I think in order for anyone to understand it, I have to explain it well.
I was flashing the new LegacyXperia ROM on my Xperia Arc S (http://forum.xda-developers.com/showthread.php?t=2545354) .. before, I had an older version of LegacyXperia already installed, with CM10.2.
Anyhow, I forgot to flash the boot.img! I did everything else as I should and istalled the ROM. Yet now when rebooting the phone from recovery, it only gets to the "LegacyXperia" screen (I don't know how this is officially called .. it's the first screen you see) and not further. Well, if I press the home button when it's starting, I get to recovery mode. .. So I've been trying my best to fix this. This includes:
Currently I have another Arc S device to work with - I have made a backup through recovery on that device (which works perfectly, running a different ROM) and tried to run it on the "broken" device .. recovery said it went well, but when starting the phone, nothing changed.
I've tried installing a different ROM (the one that is also installed on the second device), but again nothing changed.
I've tried wiping pretty much everything but the "dalvik cache" (since I don't know what this particular cache is) and installing the different rom and/or using the backup. Nothing made a difference.
I've even made an attempt on install the forgotten boot.img - I've taken the previously mentioned backup, put the boot.img into it (all that was on the SD card, via my computer, of course), and added the md5 values to the md5 file. Well, my phone was giving me a md5 mismatch, so I tried wiping everything off the md5 file, which seemed to do the trick (this is a useful thing to know!), since I was able to go through with the process of recovering the boot.img through recovery. After I've managed that, I've reinstalled the LegacyXperia ROM as I should have in the beginning. Yet again, nothing changed! the phone still won't start!
I am really desperate and out of ideas. ..the only idea I have left is try to install an older version of legacyxperia (the one I probably had before) .. but since installing a completely different ROM didn't work, I have only little hope..
I was not able to get into fastboot .. I do not know if it's enabled or not, since it was not me who installed the previous ROM on my phone. I know, shame on me ..
I hope I wrote down everything one could need in order to help me. And please do help me, I ran out of ideas and would REALLY hate to loose this phone!
I didn't understand the part of adding MD5 values to the MD5 file, but whatever
I don't really see why the rom wouldn't boot up, unless the kernel just isn't being flashed. (Maybe the previous owner relocked the bootloader?)
Can't you fastboot the kernel?
Also, Dalvik Cache can and actually should be wiped when installing a new rom.
SOLVED
Yeah, I got the feeling the kernel didn't flash, too! .. perhaps the bootloader was re-locked, but I really don't see why one would be doing that..
I was trying to get to the fastboot screen (with all the button-pressing and usb-plugging), but didn't manage that. However, I found a solution! (and god bless the guy who put this up!) I followed this thread [it seems xda-developers won't let me post an outside link .. anyhow, it's a thread on androidgadgematic.com, titled "How To Fix Bricked Sony Xperia Android Phone With Flashtool [ Unbrick ]" from june 17, 2012] and managed to install the stock ROM without much trouble. Now the phone is again running nicely I did, however, have to get a seperate driver package, since the one supplied with the flashtool wouldn't instal - I googled the drivers and used version 1.5 from xda-developers' forum.
GOSH I'm glad this is over
Related
I flashed a ROM and now I can't make it past the boot image. I'm not sure why. It's been there for the past few minutes. So I pulled battery and went to bootloader to boot to recovery and retry. Recovery and root is working fine, but somehow it says I have an update package on my SDCard....so now my only two choices are to install or not to install and reboot.
Since I can install an update package, I think it does mean that nothing vital is screwed up. I've just been checkmated.
Now how do I enter recovery? I know I can always install an HTC update package via ADB, but I don't want to lose root and have to reroot and all.
So is there some way I can get into recovery without bootloader?
Thanks
EDIT: It looks like there's some way to boot into recovery using android SDK, but I can't figure it out. Any help?
EDIT2: I don't have a micro SD card reader, so I can't delete the pesky update package (it might be some boot.img I downloaded but never got around to)
Final EDIT+ Solved
For those who didn't understand SDK and ADB, this was a great help:
http://www.youtube.com/watch?v=y6K1XLmafPc
Actually I realized that I could boot into bootloader and then recovery without an SD card. Lawd have mewcy on idiots like me When it started getting into 4ext I popped in my SDcard again and booted right in. Everything should now be fine.
On a side note, I realized I forgot to backup my previous ROM in my haste to see if MIUI Camera worked on certain ICS roms (I got it completely working in blackout, and partially working in NeroXL). I hope to god I'll like XGS, because this was more effort than I'd like to spend on my phone.
I'll leave it to the Mods decision on whether or not to delete this, maybe this info will help others.
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Let's try this in order: if you are with Virgin Mobile, it is a CDMA. GSM phones take a sim card, both versions accept an sd card for storage.
Everything looks good until:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Good luck. If you have any more questions, feel free to ask.
pedantfool said:
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Click to expand...
Click to collapse
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
followup
FIRST: Just thought of something that might be very important, I only had a version of android 4.0 installed on my phone. Will that make a difference when installing roms intended for later versions of android? If so, I feel like a huge knuckle-dragging fool.
Update: Was able to install and boot using PACman, but ran into a boot-loop.
But to follow up to your questions:
MameTozhio said:
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
Click to expand...
Click to collapse
I'll admit I've had a hard time find a definitive version of PA or really any other Rom. I've tried going through their thread here and downloading one of the "stables" (http://goo.im/devs/gannon5197/paranoid/primoc/stables/). I've also used other unofficial versions of PA (http://forum.xda-developers.com/showthread.php?t=1799372). I'm currently downloading PACman to see if that will make any difference.
[email protected]@ said:
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
Click to expand...
Click to collapse
I did flash my boot.img using the method explained here:
Copy the kernel image (boot.img file you have extracted from zip file of ROM) to folder in which you have kept your fastboot files.
In the same folder, right click while holding shift button and select ‘Open command window here’.
A command window will appear on your screen. In command window type ‘fastboot flash boot boot.img’ and press enter.
On your screen you will get message ’OKAY/Finished’. You have successfully flashed kernel. Now you can disconnect your phone from computer.
http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
riggerman0421 said:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
Click to expand...
Click to collapse
I'd like to think I'd partitioned it properly, but I keep getting a "unable to mount sd-ext" or "unable to wipe sd-ext" message when I attempt a factory reset. I've tried formatting the the mini sd and set the file type to FAT32, but to no avail as the errors persist. I know you said not to be too concerned, but I keep failing the system wipe from your next suggestion because of that error.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Click to expand...
Click to collapse
Now how important is it that I flash the boot.img after I have flashed the rom? I've been doing it beforehand, but does doing it afterward make a difference?
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Click to expand...
Click to collapse
Those both match my radio and bootloader, what does that imply? I'm planning on flashing this rom: http://forum.xda-developers.com/showthread.php?t=1948034
Will that work?
No, it won't. You have the newer updated hboot and radio. That is the source of your boot loops. The only compatible roms at this time are MyOneV, ExtremeSemse, and RhythmicRom. You can also use Cyanprimo, but you'll have flash the boot.img from RhythmicRom.
Now I've downloaded RythmicRom and I'm still stuck in a boot loop. I'm sorry for being a bit thick, but could you link some roms that would be compatible or explain what I need to be looking for?
Version I downloaded: http://forum.xda-developers.com/showthread.php?t=2147407
You'll need to download the 1.2 update, then extract the boot.img from that. The boot.img in the Rom doesn't work with the new update.
So I've been reading up on the issue over here: http://forum.xda-developers.com/showthread.php?t=2018518&page=14
and while I don't claim to understand it all, I believe I get the gist of it.
I also've managed to get RythmicRom working thanks to riggerman. I guess I'll just play the waiting game until someone rolls out a fix or just replace my phone (though that's very much in the long-run).
Once again, thanks to everyone and hopefully this will be the last we see of this mess.
Glad you got it running, and glad I could help.
I am a frequent experience Android user and have been flashing Roms since like forever.
Owning gs4 been nice installing Roms all the time however recently when I went to install new gpe ROM (new kernel seemed prime to have) coming from HDrom rls20 I downloaded currupt zip. When I tried installing currupt zip (not knowing yet it was currupt) it gave me red errors not allowing me to proceed.. Then, I turned off device got fresh dload and made sure md5 sum was legit and it was tried again of course first factory data reset with advanced system wipe the ROM proceeded to aroma installer this time.. Attempting to install I chose all my settings and it went to progress bar to install and skipped any system extraction and went straight to Apks.. Batch completed and I hadn't a ROM installed for it took it 5seconds.. I have had this problem in the past before and I sold it they returned it (didn't like condition) and bingo I was able to install Roms again (this was way back in the day with this same gs4) I'm assuming system partition not mounting because also when I tried installing that currupt file it was saying in red unable to mount system and stuff. Luckily I downloaded NK2 firmware (took 8hs) and am fine on stock but I'm hoping someone has a clue to point me in right direction.. I saw forum of somebody with similar issue their fix was pushing zip via computer adb commands then installing. I'll have to give it a try but sticking to stock for a bit. BTW this happens with every ROM just skips system files in fact cyanogenmod just hhung at installation wouldn't fail or complete. I used TWRP LATEST. Please help developers I'm sure this ones a no brainer for y'all. Except seems like issue only I've encountered for this isn't a popular thing at all on google.
SOLVED
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Stoowyguy said:
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Click to expand...
Click to collapse
What does it mean to "push adb" a phone's rom? Doesn't Odin automatically flash the selected rom?
Tearing my hair out now, I am a bit of a novice at this, but done a few phones before, it is such a minefield!!! I have googled lots and tried to fix it by following various instructions, but just can't. Can some experts please help me? Thanks!!!
I have an Xperia M, which was behaving very oddly, showing as nearly full with hardly any apps. So decided to put CM12.1 on it to see if that sorted it.
Followed official CM instructions (https://wiki.cyanogenmod.org/w/Install_CM_for_nicki) to install. Followed the process for official Sony bootload unlock, which said it had worked. Got into Cyanogen Recovery, but get odd messages when trying to do the "wipe/factory reset" step. (Odd messages like described here: http://forum.cyanogenmod.org/topic/112974-wipe-data-does-not-work/).
Tried flashing CM12.1 from SD card in Cyanogen Recovery anyway, but it didn't work. Came up with more errors along the lines of "can't mount /data".
Thought I would try to revert to stock (as described here: http://forum.xda-developers.com/showthread.php?t=2697277).
Have installed flashtool (including the drivers), downloaded an .ftf file, but when I try to follow these instructions, I point the firmware selector window at the folder I put that in and it just doesn't see it.
At the end of my tether now, anyone got any suggestions as to how I can either get CM12.1 to work (would be great!) or at least get flashed back to stock?
Thanks a lot in advance, really need some help now, have spent hours trying to do this with the help of Google!!!
I have tried flashing CWM (which worked) and using that to wipe/factory reset, and get the same errors. There seems to be something fundamentally borked that is giving me this error:
"failed to mount /dev/block/platform/msm_sdcc.1/by-name/system"
And I can never mount/format the "/data", which is related?
BUT!!!!! I think I have solved it...
...downloaded Archidroid (http://forum.xda-developers.com/xperia-m/development/rom-archidroid-v2-5-0-power-hands-t2806978), flashed the boot image for that in fastboot, that gave me TWRP, and that seemed to have extra options which successfully did a factory reset - had to do an extra "format data" which did the trick. Did the Archidroid ROM flash (what a fantastic user friendly installer!!) and it all seems to have worked - no error messages!!!
Phone restarting now, looks promising.
I hope this has worked, not really sure what I did wrong, or why Cyanogen Recovery and CWM could not fix it and TWRP could?!?!?
What fun!
Good to hear, but please post in Q&A, Help, and Troubleshooting subforum next time for these kinds of posts.
Please help!!!! I'm a noob to Sony smartphones and I did something stupid to my newly acquired C1905 sgl sim Xperia M. I tried to unlock boatloader impatiently using that app (apk) can't remember name. Anyways I've used it before on another Samsung phone and ended up in bootloops but I'm clued up on reviving Sammy's! ! And I tried it on the c1905 restarted and nothing. No LEDs no vibrations.. Nothing! ! I was impatient because I didn't have my laptop with me and seems PCs are the only way to do this on Sony's. Last night I messed and messed and the only progress after loads of forums and windows downloads I've managed to change the device (in device manager) from QHS_DOWNLOAD to the drivers recognising the device as a Sony... Will have to check again on laptop. Still no responses whatsoever from phone at all. Please help
Edit - as per device manager windows is saying "Sony Ericsson sa0101" with ADB interface driver and its working properly.
I did install loads of different driver packages. Some failed some didn't. Thanks
****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Anyone?!
edit:
hi all, after immense pain, stress and struggle to get the thing to mount, and trying everything suggested online, it eventually just like "soft-bricked" or whatever, like it was just perma-stuck on the google screen and wouldn't boot to system. i am guessing it's because after a mistake it wiped the system.
i have managed to flash it back to stock, everything is there, and/or redownloading. no way am i gonna bother again, like if it ain't broke don't fix it at this point that would be foolish thought it was perma broke. i'm gonna get a profressional to do it or something, or to give me one to one support to try it again. in the meantime i am going to learn more about rooting and the NRT and all the fundamentals of that.
if anyone here has advice about this still, or articles where I can read about it online, where to learn etc. I'd appreciate that as well, thanks.
Cam3333 said:
****** Would really appreciate some help here...
I've tried to install quick reboot (zips), magik, (zips) and busybox, on 3.4 0-0 twrp, and it won't work to boot to system, still says on this version it cannot mount the system. I don't have the perma-recovery file as I cannot find it online, and nexus root toolkit doesn't download it in the dispensaries, latest version.
Hope I haven't knacked it, i also have some screenshots but it doesn't matter as I cannot access the system itself, unless i am missing something it should just boot back to system, I don't understand what I am doing wrong, or have done wrong. Got the img and everything with it.
That said, the mount storage issue is the only thing red, or wrong in the flash, everything else worked apparently, said it installed without a hitch. Which was different that with the standard NRT downloaded twrp, with supersu, as that didn't work.
It just goes back to twrp constantly, can't boot. Help. Really wish I just waited for a response here first. Also I don't believe this is a bootloop, as it just goes back to twrp not bootloader or anything else, probably wrong.
I have been using this vid from the start: realizing that wasn't doing it, magik and a new bionic busybox zip eventually did the trick on 3.4 0-0 twrp, but it sitll won't boot to system. It is probably something obvious, I have been on this for hours today and yesterday, no luck.
only thing i can think of is something to do with: fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
basically i flashed the latest version, i dunno if it's supported by nexus 5x.
thanks. uh just please say it ain't bricked.
Click to expand...
Click to collapse
issues such as what youve experienced are usually caused by version mismatches. I dont have this device and am unfamiliar with the root process for it, but it shouldnt be too different from any other phone. what is the baseband version of your actual phone?
look at this specific reply in this thread
GUIDE - Fix bootloop with locked bootloader via ADB/Fastboot (Android M, N, O)
Hi, Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled. This tutorial works for Beta Android O bootloop too. You will need: ADB + drivers installed...
forum.xda-developers.com