Related
Hi there! Thanks for taking time reading this..
I have the GNexus GSM version. It was rooted with Cyanogenmod working JUST fine, until I decided to un-root it. I downloaded the official room from Google (http://groups.google.com/group/android-building/msg/43c3a418144fc6c5?pli=1) and started flashing the Bootloader aswell as the room with theese fastboot commands.
My problem now is that the ROM keeps spinning on the splashscreen. I can't get past it! Also when I'm trying to access the Recovery mode, there is a red triangle. I can't connect the USB to the phone as the (adb devices) does not recognise the phone...
Any idea on what I can do?
UPDATE: I managed to get "fastboot" to work now. Now it seems I can't flash back to Clockwork Recovery image. It fails when it tries to write. Same goes to flashing radio images.. Any ideas?
What I get:
sending 'bootloader' (5300 KB)... OKAY
writing 'bootloader'... FAILED
get device in bootloader
connect to pc
./fastboot flash recovery cwm_recovery.img
./fastboot reboot recovery
done, flash desired rom.
the recovery you currently have is the stock recovery.
It worked! Thanks a bunch man!!!
If you don't mind! Would you guide me to Googles official GSM rom? Because this link I posted above seems to only be an update of some sort. I was trying to flash it from Clockwork Recovery.. (I never should have taken my original backup out from /sdcard/)..
grab official 4.0.2 (there's no "official" IML74K/4.0.3 update yet) from here ; 180mb+ download;
untar it; you'll see several files, one of them will be flash-all.sh.
this is the script that you can use to automate the process of restoring to stock. if you open it with a text editor, you'll see how it does things.
now, you already have a bootloader and a radio installed, so we need to know if it's worth updating them.
bump your device to bootloader. in the left bottom corner, you'll see current installed versions.
if bootloader and radio are older than the ones provided by ICL53F tar you just downloaded, you might want to use flash-all.sh alone, once in bootloader you can just
chmod u+x flash-all.sh
./flash-all.sh
if the versions you have installed are already up to date, no need to reflash bootloader/radio, or use flash-all.sh.
among the files extracted from the previous tar archive, you see another file, something like image-maguro-icl53f.zip.
inside this will be more files like: userdata.img, system.img, recovery.img, boot.img.
we've got no need to reflash recovery.img, obviously because we have cwm already installed.
flash these separately, in order (like flash-all.sh does)
./fastboot flash boot boot.img
./fastboot flash system system.img
./fastboot flash userdata userdata.img
./fastboot erase cache
and at last,
./fastboot reboot
that should have you back to android UI, let it boot, don't send bad vibes to it
before anything else, be advised that there's a file in the rom
/system/recovery-from-boot.p
that, when reboot is called, will overwrite cwm with stock recovery. either delete this file or rename it. (ofc, you'll need su privileges, not available in a stock rom).
p.s.: there's a lot of threads that explain how to do this, not to mention official/unofficial fastboot guides. please try to search more next time.
Thanks alot man! You really saved my phone!!! I will save this for later use! I hope other people having the same problem can find this post!
Glad that you got your problem fixed but people need to stop improperly using the term brick.
If your phone is capable getting into bootloader and recovery mode then it isn't bricked. A bricked phone is a phone that doesn't turn on, unable to get into bootloader and recovery mode.
Thanks, this way it will not mislead people.
Sent from my Galaxy Nexus using xda premium
Yeah I learned that earlier today Sorry for that! Got one question thou.. The reaseon for me to restore it to stock rom and unroot it again is because I'm one of the unlucky having both signal drop issues and touchscreen bug. The signaldrop is the worst. It constantly drops from full signal to zero. Ive tried alot of roms and kernels and it fails even with the stock 4.0.1 I had when I bought it (now I have 4.0.2 after the help from bk201doesntexist)..
I don't know exactly how to ask this dumb question but I'll try.. When I now have restored it and upgraded it to 4.0.2-stock, and then flash it back to custom firmware cyanogen etc; Will my core change of software (4.0.2-stock) still be in my phone?... In other words, my signal issues and touchscreen bug might have got a fix from my 4.0.2-stock update?
You see, I've had this bug on EVERY rom I've tried. I've tried five different
keem85 said:
Yeah I learned that earlier today Sorry for that! Got one question thou.. The reaseon for me to restore it to stock rom and unroot it again is because I'm one of the unlucky having both signal drop issues and touchscreen bug. The signaldrop is the worst. It constantly drops from full signal to zero. Ive tried alot of roms and kernels and it fails even with the stock 4.0.1 I had when I bought it (now I have 4.0.2 after the help from bk201doesntexist)..
I don't know exactly how to ask this dumb question but I'll try.. When I now have restored it and upgraded it to 4.0.2-stock, and then flash it back to custom firmware cyanogen etc; Will my core change of software (4.0.2-stock) still be in my phone?... In other words, my signal issues and touchscreen bug might have got a fix from my 4.0.2-stock update?
You see, I've had this bug on EVERY rom I've tried. I've tried five different
Click to expand...
Click to collapse
i've had network signal issues before; updating baseband/radio to XXKK6 solved it for me (also updated bootloader to PRIMEKK15 at the same time, which probably isn't related in any way to erradicating the issue, although there's a nice way to test, just reflash "old" XXKK1 with PRIMEKK15 installed to see if issue still persists, i'm kinda lazy )
touchscreen bug.. you mean multitouch at the edges of the screen (there's a quick fix, just screen off, screen on again with power button, it will start working again), no, we still need to wait on google for that i think, but yes, there's a chance some good custom rom has the fix for it (cyanogenmod is a great example of a great rom), although it's not on aosp master branch yet.
note: benefits of aosp master branch - bleeding edge aosp tree. all the latest stuff go in there, is the most active branch of them all, the easier of them all to make changes in.
release tags (like 4.0.3, 4.0.1) are specific moments in the tree's timeline, hence no changes can be done after they're released - supposedly, they're stabler. Official OTAs actually originate from release tags. So you could build 4.0.3 official OTA yourself, if you cloned aosp tree and checked out 4.0.3 tag, and then build.
the master branch doesn't have a release number, it's ongoing development. to build from it is to have the latest version available of android on the date you built it.
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
Evening Guys,
so, I just tried to flash my old Xperia S for my girlfriend to use it, but unfortunately I faced a few problems. The major one would be that after wiping the phone it is somehow missing a recovery. At first I thought "No problem at all, just flashing a new one via fastboot" but in the end this did not work as well since the system could not find a recovery partition, so the command "fastboot flash recovery xxx.img" did not work. After some research and try&error I wasn't able to install a proper recovery on my phone due to the missing partition.
Does anyone here have an idea how I to handle this? I managed to reinstall an stock image via flashmode but the recovery problem still existed.
Would be great if someone would have a solution for this, even if it is a quite obvious one, maybe I am just barking the wrong tree...
jt6250 said:
Evening Guys,
so, I just tried to flash my old Xperia S for my girlfriend to use it, but unfortunately I faced a few problems. The major one would be that after wiping the phone it is somehow missing a recovery. At first I thought "No problem at all, just flashing a new one via fastboot" but in the end this did not work as well since the system could not find a recovery partition, so the command "fastboot flash recovery xxx.img" did not work. After some research and try&error I wasn't able to install a proper recovery on my phone due to the missing partition.
Does anyone here have an idea how I to handle this? I managed to reinstall an stock image via flashmode but the recovery problem still existed.
Would be great if someone would have a solution for this, even if it is a quite obvious one, maybe I am just barking the wrong tree...
Click to expand...
Click to collapse
You can use the DoomKernel for getting a recovery. It works with stock firmware too. You need unlocked bootloader for it though. You can find DoomKernel here.
Thank you so much a new kernel made the trick. Now the Xperia S is finally running 5.1, fantastic!
Sent from my OnePlus One using XDA Free mobile app
Hello all - I've been working for a few weeks (off and on) trying to get my old Incredible 2 in a working order to use as a wifi media device. To get he newer apps I needed to upgrade to at least ICS. I went through htcdev to be able to flash roms and then decided to downgrade and try to get to s-off - at which point I discovered revolutionary was down....I've since been able to get back to the htcdev unlocked bootloader process so I'm s-on with hboot .98. I'm using TWRP 2.6.3. I've tried three different roms - two cm10.2 and one cm11 and while they flash I'm not able to get past the boot screen (past the HTC one). I've done wipes before each flash and I've flashed the correct boot.img each time. I've tried each one of them at least twice to no avail. Is there any other settings or things to try??
My ultimate problem is that I was able to get to Android 4.2.2 but the app that I need to play my music from the cloud is Microsoft Groove which due to a recent change is no longer working with 4.2.2 (kind of like the perfect timing I had with revolutionary being down) - so I'm trying to get to something higher than that...Any other ROM ideas might help too???
Thanks. I've learned so much following this forum over the last few weeks - I just can't seem to get past this one by myself.....
Well thankfully I was able to solve my own problem...Figure I'd update here in case anyone else comes across the same issues. I basically did not have the best TWRP version installed - you need to have TWRP 2.7.0.0 installed. Once I installed that recovery I was able to flash each and every rom and the phone is starting up fine (after also flashing the correct boot.img file). We'll now see if I can get past the app issue itself that I was having but I'm definitely past the boot screen issue.
I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
bigdog1459 said:
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
Click to expand...
Click to collapse
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
nastyneighbor said:
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
Click to expand...
Click to collapse
Damn. I'm sure you have tried some of the manual flashing guides out there too?
nastyneighbor said:
I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
Click to expand...
Click to collapse
Not sure when you said you used "Stock Recovery Flash Tool" if you meant the "Android Flash Tool". But just in case you didn't, that can force flash partitions with it. Probably your best shot.
Android Flash Tool
flash.android.com
Android Flashing Tool online unbricked me the other day. You have to be patient with the tool as it took me several tries. It will totally wipe your phone, but at this point you just need to rescue your device. Keep us posted.
thanks for the tip. i'm trying the android flash tool again now. and will keep trying it until it at least passes the download stage. and yes i tried all the manual flashing guides out there...and hybrid combos of all as well. i mean i'm positive its my fault for missing SOMEthing somewhere but many hours have been spent with overall negative progress.
my track record is still zero hard bricked devices or soft ones I couldn't fix over all these years so i'm not too worried but i could use my phone back haha
will keep posted as requested. ty again.
I know this doesn't help your immediate situation, but when flashing anything like custom kernels, I would advise not to use some random app to flash it with, just follow the directions in the OP of the kernel's thread, and make sure you have up to date Platform Tools and driver. CleanSlate and many or all the custom kernels also require flashing more than just the boot.img.
Good luck, I hope you get it back working for you.
Hey guys, the Android Flashing Tool finally worked for me and I am up and running again. Thanks for your help and tips. Hacking phones is more important every year and thus I truly value your skills and advice. This community must survive the new world order. much love folks