I am new to cell phone mods. My goal was to gain some experience by rooting and replacing the os image on my Atrix 4G. I use it for my alarm clock which uses an application that won't run on newer version of android than v2.x.x. I successfully rooted and installed super use. I then installed Titanium Backup and did a full backup to sdcard. I installed Rom Manager, chose ClockworkMod Recovery and then the correct image, and told it to flash the recovery partition. Rebooted. Got an error with the android logo and a circle with a triangle. Went back to all the how to's and attempted to install unlockable_bootloader. It now comes up to rsd, seems to fail, then goes into fastboot. Fastboot devices sees it and I can reboot from fastboot but it goes back to the same place. HELP.
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Try this guide. http://forum.xda-developers.com/showthread.php?t=2262869
ravilov said:
Forget about any and all automatic methods, including ROM manager and similar. Good old-fashioned manual methods work best.
Click to expand...
Click to collapse
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
flash recovery failed
andresrivas said:
Ỳou need to download the image of the recovery partition and flash it using fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I previously found a thread that described that process and tried it. Fastboot reported it failed flashing recovery.
That usually happens if the BL is not unlocked (properly).
Phatdaddy said:
I think I have read all the posts and how to's on manually flashing. Temporarily recovered but persued my goal of learning something. Only thing it can do now is fastboot when I hold the volume key UP while restarting. Used to be down but that's gone. RSD protocol is no more. Says "Failed to boot 1" when restarting. Something I flashed apparently relocked the boot loader and who knows what else I've screwed up. Fastboot -w indicates it cas erase the cache and userdata partitions. Surely there is still hope for this as I can still access fastboot. Can you give a little help please?
Click to expand...
Click to collapse
reflash the pudding sbf to unlock the bl, then go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
flash boot failed
palmbeach05 said:
reflash the pudding sbf to unlock the bl, th
en go ahead and flash recovery as advised. if I remember correctly, when it says failed to boot 1, its automatically in rsd, which means just hook it up and let rsd lite do its job then fastboot for recovery
Click to expand...
Click to collapse
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Phatdaddy said:
Installed pudding successfully with RSD Lite. Attempted to flash recovery with "fastboot flash recovery image_name". Reports "sending recovery" and then "writing recovery". When I reboot, it still has has the stock recovery utility.Otherwise, I'm back to stock 2.3.6 except that it reports unlocked upon rebooting. Am I not flashing the correct thing? Thanks for the pointers.
Click to expand...
Click to collapse
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
palmbeach05 said:
hmm, sounds like you're on the 145 build of 2.3.6. Check to see what your phone says in about phone. its going to give you a system version ending in 141 or 145.
Click to expand...
Click to collapse
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Phatdaddy said:
This one says "4.5.141". Before undertaking to hack this piece, it was 4.5.145. I have flashed preinstall and boot and attempted to flash recovery. I don't know where it stores the build number. Could it be reporting .141 while really .145 ? I am confident the .145 is correct because we have two phones purchased the same day from same vendor and the other reports .145. I also remember it as .145 but my memory is pretty faulty.
Click to expand...
Click to collapse
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
palmbeach05 said:
ok. I think the file we need to look for in order to fix this is in system/etc. its called install-recovery.sh and that file forces stock recovery to be installed. delete that file and try flashing the custom recovery.
Click to expand...
Click to collapse
ls of /system/etc/install-recovery.sh says the file does not exist.
When I bricked my atrix i used the xatrix tool to unbrick it. works really well and once unbricked was fully unlocked so was easy to flash new roms
xatrix (dot) webs (dot) com
once on there website click to download tab to get the downloads
This tool will remove everything from phone root, unlock and install cwm. What you do after that is upto you. sometimes its easier to start over then figure out what went wrong when installing a mod.
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
And thats the part that confuses me. It says 141, but the recovery issue is acting like its a 145. I'm stumped, but i do believe there is an install-recovery.sh script or something thats preventing this thing from sticking after flashing. I'm really baffled by this b/c i ran 141 for the longest time, i did all my rooting, unlocking, and recovery flashing on 141, and got no issues. I could advise that you download and flash the ICS leak (the true leak, not the ROMs we have available) via fastboot and see if that changes the situation, but i don't want to advise you to do something and then a bigger mess appears.
Sent from my MB886 using xda app-developers app
Phatdaddy said:
My problem is now this, I'm recovered, rooted, and unlocked. If I flash recovery with fastboot, it says I am successful but when I reboot the original recovery image still exists.
Click to expand...
Click to collapse
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
overboard1978 said:
sounds like you had 145 installed and flashed 141 over it without doing a wipe first. i would use cwm recovery and do a factory reset wipe all data and flash the rom you want to run.
Click to expand...
Click to collapse
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
palmbeach05 said:
he can't get cwm installed. it may say it gets flashed correctly, but he cannot get cwm to show up and be usable.
as a work around, via fastboot, run the commands:
fastboot erase data
fastboot erase cache
that would cover what factory reset does.
Click to expand...
Click to collapse
That should do it. If for some reason it doesnt the xatrix tool will wipe everything off the phone and start it over with 141 unlocked bootloader, with cwm. Only automated tool i found that will unbrick phone with rsd lite. Make sure phone is fully charged before starting xatrix tool as it wipes battery fast and if it dies you will need to start over.
Erase cashe was successful, erase data failed. Found reference to additional file to delete but it did not exist either. If I conttinue, I will repost. Thanks for everyone's effort trying to get this working.
Related
I used the System Recovery app to flash recovery and boot into it, then I installed Neutrino ROM EE but now when I try to boot all I get is 'failed to boot 2. starting RSD mode.' help?
bjgrenke said:
I used the System Recovery app to flash recovery and boot into it, then I installed Neutrino ROM EE but now when I try to boot all I get is 'failed to boot 2. starting RSD mode.' help?
Click to expand...
Click to collapse
Is our phone bootloader unlocked if No u will have to unlock the bootloader first.
And check this thread
[Updated 1-7-2012] THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
I don't think the bootloader is unlocked, and I'm not sure how I can do that since I can't boot.
Is this a brick? Or is there a fix for this. Need help here people.
bjgrenke said:
Is this a brick? Or is there a fix for this. Need help here people.
Click to expand...
Click to collapse
As terminator 1983 said, you need to unlock your bootloader. Click through the link that was posted and read up on the unlocking process. You'll see that involves being in RSD mode, and flashing the pudding .sbf. Then reflash CWM, and re-install your ROM.
Alright, I clicked the link, and scrolled down to HOW TO UNLOCK BOOTLOADER. The first option, the link is dead. The second option, which seems to be easiest, the download link is dead also. Is there any other way I can get the file "Full 2.3.4 with preinstall root and pudding bootloader unlock, full sbf" ? Then using RSD Lite to flash that should be all I need.
Also, in that second option, I scrolled down to the second post since I'm not an ATT user, and tried doing the CMD commands, but when I put in the first command "fastboot flash preinstall preinstall.img" it says this is not a command.
bjgrenke said:
Also, in that second option, I scrolled down to the second post since I'm not an ATT user, and tried doing the CMD commands, but when I put in the first command "fastboot flash preinstall preinstall.img" it says this is not a command.
Click to expand...
Click to collapse
make sure you run the command from the same folder your fastboot.exe is at. Also, any file you are trying to flash has to also be in that folder.
i.e. fastboot.exe and preinstall image are in c:\atrix, then cd into c:\atrix and then run your commands.
Sorry, I can't help with the dead links.
*Edit*Btw, you can just get the pudding .sbf from here, instead of using the automatic ones.
Alright, moved fastboot and the img into the same folder, ran the commad, and it says the following:
"sending 'preinstall'
OKAY
writing 'preinstall'
FAILED (status read failed (unknown error))
finished"
followed the link you provieded to the main pudding thread, downloaded the IHOP file for international useds, flashed the SBF succesfully, but I'm just where I was before.
When following this guide http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader I type in the command in fastboot and it says OEM Fastboot Not supported.
Need help here guys.
Edit: Tried again and it gave me my code, redid the command with the code, this time it said ERROR: Failed to write.
Okay, making progress now, checked my phone and it said Your phone is not unlocked. Rebooted and not instead of saying Unable to boot 2 Starting RSD Mode, all it says is unlocked. I'm able to get into recovery mode, but it's the default android recovery in blue. What else can I do?
bjgrenke said:
Okay, making progress now, checked my phone and it said Your phone is not unlocked. Rebooted and not instead of saying Unable to boot 2 Starting RSD Mode, all it says is unlocked. I'm able to get into recovery mode, but it's the default android recovery in blue. What else can I do?
Click to expand...
Click to collapse
Glad to hear you got it unlocked. I would recommend flashing romracer's recovery. Make sure to read through the first 2 posts of that thread. There is a file you have to delete in order for it to stick. Since you're familiar with fastboot now, I would just use that method to install.
After that, follow the instructions to install your ROM of choice.
ghost_og said:
Glad to hear you got it unlocked. I would recommend flashing romracer's recovery. Make sure to read through the first 2 posts of that thread. There is a file you have to delete in order for it to stick. Since you're familiar with fastboot now, I would just use that method to install.
After that, follow the instructions to install your ROM of choice.
Click to expand...
Click to collapse
I've downloaded the Light green version, placed the img in a folder along with fastboot and the 2 dll files associated with fastboot, ran cmd to that folder, typed in the first command, and it says it's not an external or external command. Is there something else I should be doing?
Whattheheck, may as well copy what I posted on another forum for some additional info:
Hello, I've been on many forum sites looking for a fix for my problems, but nothing SO here's my story. I have a rooted Motorola Atrix on Bell. I installed the app "System Recovery" and used that to flash recovery, then booted into recovery and installed the rom "Neutrino Rom EE". The problem is, I didn't unlock my bootloader, so every time I tried turning my phone on it'd say "Failed to boot 2. Starting RSD mode." I used the guide "How To: Unlock the Atrix 4G Bootloader" on Breifmobile (can't post link) to unlock my bootloader, and from what I can see (my phone being stuck at the boot screen with a motorola logo and the word UNLOCKED in the top left) it worked. Problem is now I'm stuck here. I can access the menu by holding pwr and vol down, then I can select an option. I tried selecting Android Recovery, and this brings me to the default recovery, but there's nothing I can do here. I can still access RSD mode and Fastboot from the menu, so perhaps there's a fix from there.
Anyone? Need my phone for a meeting tomorrow
bjgrenke said:
Anyone? Need my phone for a meeting tomorrow
Click to expand...
Click to collapse
Download CWM recovery img file from here (not the zip one)
[Unlocked Only][RECOVERY][2011-11-14] Custom CWM-based Recovery 5.0.2.7-atrix5
Place the recovery img file in fastboot folder and type these commands on command prompt after getting to fastboot folder.
fastboot erase recovery (it will erase the earlier recovery)
fastboot flash recovery recovery-blue-atrix5.img
The second command will flash the recovery img on your device you will have to change this portion "recovery-blue-atrix5" of the command according ur revcover img name or rename ur recovery img with this name.
Hi Moto guys
I bought this RAZR. It is a GSM one without operator customizing.
I rooted it normally and tried to update to ICS leak (this one if I remember well).
It didn't work.
Anyway I downgrade back to Gingerbread and tried to flash in recovery the MIUI V4 zip.
It bootlooped.
So I wanted by the same way to downgrade to 2.3.6 again.
It was a fail.
From this, I had the flash failure screen at the beginning and lost the recovery.
Because of a "Battery Low" I made a factory cable and I can access again to the "flash failure" screen.
I found a tuto relating to the same problem than me and tried to apply it.
I downloaded this rom (SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.xml.zip) as explained and tried to flash it in RSD lite.
The problem is:
I have no error message, it just stays stuck on "6/11 flash system "system_signed".
I let it several hours, it never passed away this step.
With "Eternityprj_Fla**** script it's the same, it's blocked at "system writing..."
I don't really know if I'm considered to be on ICS or GB. My bootloader version is 0A.75 so I guess ICS one.
Any idea to reanimate this XT910?
Thanks for the help you could bring to me
P.S: I tried these roms since the first fail
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-DE_1C.91P_0A.6C_TMDE_CFC_HWp2b_SIGNED.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-1-FR_SIGNEuropeAustraliaEMEA_USASPDRRTFR_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-73_SPU-11-PASS-10_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
-SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml.zip
Since I use XP in a VIRTUALBOX machine, I have an icon with activity on device.
During this operation, the activity on the phone is important
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe flash system sy
stem.img
sending 'system' (793344 KB)...
OKAY [ 28.541s]
Click to expand...
Click to collapse
As it is to this step, no activity...
writing 'system'...
Click to expand...
Click to collapse
I tried with normal fastboot executable from SDK and erpj-fastboot.exe, no difference.
Is it possible I make something wrong with my factory cable?
I don't think so because it makes my phone booting as I plug it and it writes normally boot.img for example with fastboot.
Your help would be appreciated very much guys ^^
Thanks!
Solved!
I can't explain why but I managed to access recovery even if system flash with fastboot never ended.
I flashed ICS rom and it booted well.
So it's solved even if I can't give explanations.
Thanks anyway.
flash fails...repeatedly
This has been covered extensively, but mine is still screwed up, i rooted the phone with clockwork mod. When the official ICS cam eout, i tried to manually download it. I have unrooted the phone and tried to install ics, it failed. So i tried flashing back to factory because clockwork was still popping up on boot. The flash continues to fail. I have tried using moto-fastboot in command prompt, i ha tried rsd lite with the flash(4 different ones). It keeps failing and i end up in the ap fastboot mode. it takes 2 tries to get the phone to boot normally and occasionally the clockwork boot menu pops up on reboot. Any ideas how to just start from scratch. As seen by the problems i have caused myself, i am a complete amateur here.
A little info, the phone is about 8 months old, rooted it once successfully, it is currently unrooted(i tried to reroot but got hung up in ap fastboot), updated drivers twice, moved the flash files all arounf my computer, using windows 7 64 bit. thanks to anyone who may help
Ok ok ok...
if i have an advice, before flashing, read read & read again.
So now.
Give me more info about your phone(xt910 / xt912 / europe / asia / latam /usa ) ??
Can you rsd to system_signed, or flash it manually through fastboot ?
When you installed ics manually which error did you have?
If you can, try to flash system_signed then reflash the OTA package with official recovery & wipe data. But i guess it wont work. For now i can't help you more without more info.
So tell me all you can and write it clear.
Or try this through rsd lite or fla**** http://forum.xda-developers.com/showthread.php?p=28199183
Sent from my XT910 using xda premium
yes, now ics fastboot file is out, you can easily fastboot to get back.
it is usa...i am downloading the ics fastboot now. I have tried the fastboot method with the latest gingerbread build, and also using the command prompt and flash commands....will let you know
thanks
Flash failed right away....how do i know i have the correct drivers? any other ideas?
I had the same issue when attempting to flash. Make sure you switch to a usb 2.0 port.
After that find the moto-fastboot package and then flash all the files manually using moto-fastboot instead of regular fastboot.
You have to do that for every single file. The file names are in the xml in the fastboot file.
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
Hi guys, after 10 hours of trying to get my P760 to life I finally, as a last resort, decided to open this threadh. Heres the deal, my friend gave me his P760 which was stuck at the boot logo, I firstly tried to fix it with LG mobile support tool but it got stuck at 15% after countless tries. Then I tried fixing it with Lg flash tool but it also gave me some errors "omap factory download fail lg p760". After that I couldnt access S/W mode anymore nor did the phone turn on, only black screen. When I connect it to my pc it just makes sounds of new device connected/disconnected. I tried this fastboot method http://forum.xda-developers.com/showthread.php?t=2292828 but couldnt make it work. Is the phone completely dead or is there anything more I can try? Any help is appreciated, thank you very much.
What was done to brick it in the first place?
Sent from my KYOCERA-C6745 using Tapatalk
I am not sure, my friend brought it to me and he didnt know the reason. Anyway I managed to get into fastboot on another computer and i tried to flash x loader and uboot with the bulit in options and i get the following error "FAILED (remote partition doesnt exist). What can I do next? Thank you for the reply.
EDIT I have tried to get the phone in S/W mode using this guide http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4 but I couldnt do it.
I am sure I have to flash something in fastboot so it would be great if someone could point me to exactly what. Thanks again.
EDIT 2 I tried to flash xloader and u boot from post #7 http://forum.xda-developers.com/showthread.php?t=2242444 and it gave me the remote partition error failed again. Is the phone "officially" dead?
My experience with this phone is that it is basically unbrickable, at least software wise, thanks to omap4boot. Fastboot is basically telling you the partition you specified doesn't exist. Check you are using the correct syntax. It should be fastboot flash u-boot u-boot.img and fastboot flash x-loader x-loader.img (I am assuming the files are named u-boot.img and x-loader.img).
Another possibility is that the partition table of the phone somehow got corrupted. In my opinion this is very unlikely, but it could happen if the phone is disconnected while flashing the GTP table with LGFlashTool. Let's hope that's not the case.
Good luck.
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Maha23 said:
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Click to expand...
Click to collapse
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
EdwinMoq said:
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
Click to expand...
Click to collapse
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Maha23 said:
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Click to expand...
Click to collapse
I'm seeing you using lelus method to fastboot...
1) Be sure you are in fastboot whith this command: fastboot devices
2) if the l9 is still in lg logo, just flash a recovery img into boot and recovery partition:
a) fastboot flash boot recovery.img
b) fastboot flash recovery recovery.img3)reboot the device, it must enter in recovery mode by force.
4) once in recovery just flash a custom rom as you wish
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
lecorbusier said:
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
Click to expand...
Click to collapse
Thanks for the reply. How do I perform the force hard reset? Yes, I couldnt get fastboot to work on win 10, on win 7 it works flawlessly.
Sent from my LG-D855 using XDA-Developers mobile app
Hello,
I have exactly the same problem with my p760, fastboot works so far but remote partition error and the phone stays always completely black.
Is there someone who has a new idea to fix it?
Hey,
I found this: http://massimoronca.it/2016/03/17/fastboot-failed-remote-partition-does-not-exist.html
but i dont really understand it, can someone help me?
Maha23 said:
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
readme again... try to flash a recovery.img into the boot partition
fastboot flash boot recovery.img
and then reboot... this foce the l9 to enter in recovery and then you can fotmat partitions in wipe options
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
Elsewhere you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
Hard reset is 10s power.
Such a swap of recovery and kernel could have happened after unbricking the phone, when the key combo for fastboot produces the LG recovery. That's why I flash stock twice, then it's right again & ready to root, install TWRP etc.
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Maha23 said:
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Click to expand...
Click to collapse
you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
puntoazul said:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Srsly?
recovery partition image on boot?
Probably true. That would explain the strange behaviour of the key combos during boot, after unbricking the phone for the first time. The recovery has replaced the kernel, but the phone can still boot. Strange. Fastboot is unavailable, and the key combo for the recovery shows the "dead droid" and performs a factory reset.
Groszexxx said:
Srsly?
recovery partition image on boot?
Click to expand...
Click to collapse
Yes... is an effective method to boot by forced on TWRP or other recovery and then proceed to format all partitions and flash any rom consecutively. After flashing any rom the boot partition is rewrited by the boot.img of the rom.
I did this before on my own L9 for repair and other friends devices. Is totally safe
By the way, I'm not in warn
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.