My phone is currently stuck at the "TATTOO" boot image and i have rooted my phone. I tried to install OE and Fyodor respectively and each time it gets stuck at bootloader. I have put them on my SD by just copying and pasting the .ZIP of each (not at the same time). WHen they failed i did the factory reset thing in the recovery page thing. I can't load even after factory reset help! I used this root and goldcard tut at the theunlockr site - i used the link in the page to goldcard b4 rooting. (i didn't use a SD adapter, I did it straight from my phone.) If so how to do i unbrick or unroot or atleast fix my phone
I have fixed my phone by using a Update thingy with FastBooot USB. I can root my phone successfully i think. But what i think i messed up on was with the foyodor ROM install. Can somebody post or PM me instructions on how to install it because i don't get how to install it or any other ROM
Did u look in the Development Forum?
- http://forum.xda-developers.com/showthread.php?t=645742 (from Zecanilis, very good)
- http://forum.xda-developers.com/showthread.php?t=603286 (regarding to flashing the Tattoo)
Related
Hi all,
Well, that's the way, it sometimes goes....
On Tuesday i received in exchange my new Vodafone Magic. After only two days i'm stuck with a "deadlock" situation. Following happened:
The Magic was delivered with the standard 1.6 Donut on it. I then manually flashed the OTA update to 2.1.1 and the apps that I use regularly. Yesterday I used the "Gingerbread.apk from the XDA forum to gain root. Armed with root, i downloaded Rom-Manager from the Market and installed ist. Next, i installed the Clockwork Recovery via Rom-Manager. Then reboot into the recovery and Voila .... Clockwork recovery.
Ok, first thing i did was to make a backup of my current ROM and then came the big mistake ...
I wanted to have a black Notficationbar in OTA. So i flashed "blackbar.zip" from "http://www50.zippyshare.com/d/43974308/12150/blackbar.zip". But after reboot it didn't work (Bootloop).
Well, I thought I reboot back into the recovery and restore my backup.
And then came the shock ...
What I saw then was not the Clockwork recovery but the original HTC Magic recovery.
Ok, tried to flash the 2nd part of the OTA Update again.... Nope. The HTC Recovery reports "Assert Failure". Obviously checksum tests are done and after flasing the blackbar, "framework-res" no longer matches the checksum.
OK, so back to 1.6 with the NBH Image .... Nope, The Magic reads the image, but refuses to install with the comment "main version is older"
Since the OTA update, installs an "S-ON" Spl, no more fastboot...
Searched in Google and found a lot of Posts saying "try using this image", "try using that image", but nothing worked.
So the Situation now is as follows:
- Magic can not start anymore. Bootloop in the "android" Bootscreen
- Fast boot is not possible because of the SPL
- New import of the OTA update, part 2 not possible due to checksum error
- Back to 1.6 not possible due to "Main version older"
- I only have the the original Magic Recovery. (and of course can boot into HBOOT / FASTBOOT mode)
What I would need would be a flash-ready image of Enginnering SPL or an update, however, in the format, which is accepted by the original recovery of the Magic. I also dealt with the idea of creating a Goldcard. Could this be a way to save my Magic?
Has anyone else an idea, or anyone knows how to create a flash-ready image, which is accepted by the original recovery?
Thanks and greetings. lagloose
Is this a 32B or 32A? I've been in that situation before. If you can get into fastboot you can save it. Get a RUU (for 32A I used 3.5.401 from Rogers) and install it. In the process, it'll try to get the phone into fastboot mode, but it's already there, so you'll factory-reset it. After that, you can apply an Engineering SPL through update.zip (using the recovery from the RUU itself, not AmonRa or others's) and then you can do anything else you want on your device.
Good luck! ^^.
I think you're going to have to make a goldcard, which is a problem since you can't boot. If you can somehow make (find?) a goldcard then you should be able to flash a RUU. Can you post you're device specs? Vodafone Magics are supposed to be 32A's right?
I don 't know your phone information,but i think you need a goldcard and flash ruu
if you are stuck in boot loop or having difficulty starting your phone, don't worry, there should be a way.
I have experienced this issue today after flashing wrong file causing my phone to stuck in boot loop. after searching in this forum and after spending over 3 hours, I finally managed to restore my phone and it is now working perfectly fine.
therefore, I thought of making a basic guide to try to resolve such issues. please note, this is a very basic guide to resolve problems with starting your phone, I am not professional but will try to share my experience and help anyone in need. this was done on X10i
lets start:
1- if you have a recent back up and have access to xrec, you can simply restore your phone
2- if you have access to xrec but don't have a backup, try to flash a new ROM
I tried the previous two steps but it kept saying can't mount SD, therfore try the following
3- if you don't have xrec access, use the flash tool
download from here http://www.multiupload.com/7H4JT35B6G
then flash generic 2.1 to your x10, I used this one http://www.mediafire.com/?sqv6274anzfzn2x
here is the guide on how to do it http://forum.xda-developers.com/showpost.php?p=10879528&postcount=3
I have had problem saying "install or re-install drivers", you just need to install the file in the drivers folder in the flash tool main folder and restart the flash tool program
4- after flashing this ROM, restart your phone and root it using the flash tool, after the root your phone will restart, then you need to ask for premession and click xrec to install xrec to your phone
5- before installing new ROM, please make sure that your baseband and karnel is compatible with it (because the ROM you flashed earlier has old karnel and you will be stuck again in the boot loop if you flashed 2.3.3 just like me, then you will need to start again and install new karnel before instaling 2.3.3 ROM or even restore 2.3.3 ROM)
(you can simply install the new ROM then restart in flash mode and flash the new karnel .71 or flash the karnel and restore your backup)
I know that my choices of flash tool version or generic 2.1 version might not be the best, but I used them and resolved my issue and hope it will resolve yours. for any question please do not hesitate to ask me.
credits to everyone who helped, I can't remember everyone because I read quite a lot so please forgive me
nice post my friend
In flash tool I'm getting an error:
ERROR - USB\VID_0FCE&PID_ADDE\5&2BFAB030&0&5
any idea what to do?
it sounds to me that u may need to install the semc flash drivers.. inside the flashtool u may find a folder named drivers, go inside of that folder and install ggsetup.. also do u have pc companion installed?
tripico said:
In flash tool I'm getting an error:
ERROR - USB\VID_0FCE&PID_ADDE\5&2BFAB030&0&5
any idea what to do?
Click to expand...
Click to collapse
can you post the log from the flash tool so I can see at which step exactly this massage came up
I am fairly novice when it comes to flashing so here's a pretty dumb question:
I have an X10a, can I use the X10i software that you've linked in your post or is it just going to brick my phone.
So this is my story,
I had a stock rom lg g2 d802 phone working, but didnt had a micro sim yet so i decided to flash a nice rom (http://forum.xda-developers.com/showthread.php?t=2505682). So i followed everythin as described, but then... when i finishd flashing the rom i noticed that nothing has changed in the lg. it was still the same with everything on it as before.
So my stupid brains decided to make a Wipe! in TWRP (the one where you need to type yes to continue) and after that reflash the rom i wanted. So i did just that, resulting >>> a clean sweap on my phone, everything was gone, even the rom i put on the sd card.
Not that big a deal, i just use ADB and push it on my phone, (did just that) and in TWRP i installed the rom, everything goes as supposed to. But when the reboot promt comes and i reboot to System, im getting back to TWRP.
I tried to flash the following
1. A backup i made of the phone (no result)
2. flash rayglobe (http://forum.xda-developers.com/showthread.php?t=2493209, no result)
3. flash the previous rom (no result)
at step 2 tho (rayglobe) when i flash it, i get the installer and work my way trough it, when i reboot my phone it gets back to TWRP (offcourse) but then i notice changes, like i put my ray.zip in /sdcard/ and its gone (cant see it) but i can still press the space where it was before, and it will display the pressing-animation, but wont do anything else.
i also restored my /boot folder with the one in /boot (phone side) thought it might help. no result
Then i moved on to the LG mobile support tool and put the phone in download mode (firmware update) the tool recognizes the phone but it gets stuck at step 2 (the download part) and the text in the tool isnt updated (displays chekking pc status) while in the download part. around 14 sec in from starting the upgrade in the tool. so this has no result 2.
i have tried drivers from:
google android
google sdk manager
lg android driver
lg united mobile driver
universal adb driver
with some i cant do adb and with some i can, also with some i cant do sideloader and with some i can.
but with all i cant do fastboot.
as of now i have 4 "boots" i can get into
1. recovery (TWRP)
2. download (firmware update)
3. reset factory settings
4. hardware key settings (to use buttons as phonecall helpers )
summary:
i can boot into TWRP and flash/instal/backup but with no result
what i want?????
I WANT MY STUPID BRAINS REMOVED, also i want to get back to stock or any rom that works (pref stock, got backup via TWRP) asap.
how do i manage this?
so feel free to to help me out here
going to c captain america, will be back in a while, please please please help me out
I eventually decided to flash Kitkat onto my Defy+.
Followed this guide here:-
http://forum.xda-developers.com/showthread.php?p=52342403#post52342403
Everything worked fine until I got to the actual flashing of the KK Rom. TWRP had loaded fine but insisted I had no OS installed and on exit suggested device was not rooted?
Phone kept saying failed and to re partition. So I tried the Resize.zip from another guide. This did nothing either , still the same.
It had also had the following error, "Error Executing Updater Binary In Zip".
So I tried the solution here:-
https://kalitutorials.wordpress.com/2015/06/19/solve-error-executing-updater-binary-in-zip/
Now I cannot boot into TWRP or Clockworkmod recovery. When I try to boot phone it just sits on Motorola Sign but doesn't progress and no led flashes to enter TWRP. Battery needs to be removed to switch off.
If I power up with Volume down pressed, I get picture of Android Green Robot standing up with an yellow exclamation in a white lined triangle. No options are shown.
Pressing Vol up and down I get me to Android System Recovery <3e>. Options there are, reboot system now, apply update from sdcard, wipe data/factory reset, wipe cache partition.
I can also enter bootloader using vol up and power.
Any ideas anyone, found this guide to try to fix but don't want to try anything else without some confidence it will work.
http://www.tech-zealots.com/tutorials/unbrick-motorola-defy-or-defy-100-working/
I have a nandroid backup created in normal recovery btw. I would prefer to flash back to it if possible.
Thanks
G
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
dc239 said:
You need to download a sbf file https://mega.nz/#!915TCAAD!X7_f1t83lVPkK5p7jUdokeE4SQ8qTRqPnBWNvfgyxWA (this one is stock android 2.3.6), then you need to install drivers and rsd lite and connect your phone (must be already in bootloader mode) to your pc and then reflash the sbf file. After that, your phone will boot up to the stock firmware and you can install cm11 then. Basically you can follow up the the guide that you posted. Good Luck
Click to expand...
Click to collapse
Thanks for your reply.
Tried what you suggested but after flashing that sbf the phone tries to boot up but after logo drops back to bootloader 9.10 with ERR:a5,69,35,00,27 .
I managed to get the Retail UK sbf referred to here:-
http://forum.xda-developers.com/showthread.php?t=1421526
Tried flashing it but end up with a black screen bootloader and just white led lit. Reflashed the sbf u suggested and back to Bootloader with Err.
Googling seems to suggest I am just needing to get the right sbf for the phone.
I have the Nandroid backup made with Clockworkmod recovery. Is there anyway to flash it?
TIA
G
Sorted
After extensive digging and climbing the steep learning curve. Decided the problem was that the sbf file u suggested was DFP 231 and possibly my phone was DFP 2311. Found Firmwares here:-
https://firmware.center/firmware/Motorola/Defy+ (MB526)/Stock/
And downloaded the DPF 2311 Rom, only was one. (DEFYPLUS_U3_4.5.1-134_DFP-2311_BLUR_SIGN_USADEFYEMARAB1B8TFDE004.0R_PDS03C_USAJRDNGIBRO2DE_P020_A025_M002_Service1FF.sbf). Tried flashing it and voila system is back, albeit it started up in German.
Gonna try the rooting mehod here:-
http://forum.xda-developers.com/showthread.php?t=1820282
For anyone elses benefit, the links for Roms at Android Developers don't work. The retail EU Firmware mentioned in the rootong guide is available on the site referred to above. U can tell when you click the link to the Android Developers site as the browser URL shows the full file name as follows.
DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
The rooted one I think is the same one you linked me to and is still valid in the Rooting guide too.
Thanks for all help and I hope this is of use to someone else.
G
Minor question still remains.
If I am trying to install Kitkat rom. DO I still need to Root phone if the rooted 231 has been installed, I presume not?
G
Followed rooting guide and so now have a rooted 231. All good
Now for KK.
G
Hi all,
I got a brand new Wileyfox Storm which I liked to have rooted. When I booted the phone I got several updates which I installed first.
After updating I followed this guide: http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992
And also with a little bit help from the Cyanogen wiki: https://wiki.cyanogenmod.org/w/Install_CM_for_kipper
Reason I chose for this method is because I tried the recommended WinDroid Toolkit before but the server doesn't has the required files anymore so that program is useless for the Wileyfox Storm.
I'm running Cyanogen Os version 13.1.2-ZNH2KAS3NA-kipper btw (offical FOTA).
When I followed Bobslesbricoleurs tutorial to unlock the bootloader I got a message but not one I expected. It said:
<bootloader> Device already : unlocked !
OKAY [ 0.000s]
finished. total time : 0.000s
Does this mean I got my Wileyfox Storm with bootloader already unlocked? That how I read it...
I continued to start rooting it, but not before testing if I could still boot but everything was fine.
I tried to flash the attached custom recovery I got OK and a 'remote: size too large' error. It didn't successful flashed the recovery.
I checked if everything still was ok and it was. I could boot and everything.
So I tried something different. I'm not new to flashing (I've had a Galaxy S2 for 5 years which was running on CM13) so I went to the Cyanogen site and downloaded the latest stable (snapshot) recovery for kipper which was cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kipper-recovery.img.
I tried to flash that recovery and it succeeded. I could still boot recovery and system... except that after booting system the ROM would replace the recovery back to stock.
I did some research on this but I couldn't find any helpful information about it for the Storm device. So I Googled it in general and read somewhere that COS had a developers toggle to disable 'updating recovery'.
This is probably where I made my mistake because I unchecked that update recovery toggle and reflashed the snapshot recovery that worked before.
I'm not very sure, I should have written this down, but if I remember correctly the system could still boot.
I didn't know how to flash the SuperSu-v2.46_signed.zip with fastboot, the tutorial didn't specify this and I'm used to flashing from recovery (fastboot is kinda new to me, although I have worked with adb commands before).
So I booted the rom, installed AirDroid to push the zip to my internal storage and I went back to the recovery.
I flashed the SuperSu-v2.46_signed.zip with the update option in the recovery.
And now the rom is in a boot loop.
I already tried a full factory reset but it's still boot looping.
I know that in the tutorial topic FluffyTwit has had a similar problem, not sure if it's the same but it looks like it.
The given solution is "Flash stock boot.img from stock rom zip, reboot" to which he replied " flashed the whole .zip file because I saw a tutorial on some website...".
But at this stage I'm a bit afraid that I'll do it wrong again, as the instructions are either out-dated or they're just not 100% correct. Could someone help me out and/or confirm the exact steps I should do to get my device back up and running?
I'd rather keep the device stock without root than rooting it with risks of bricking. I have a feeling this device isn't as safe to rooting as I'm used to..
Thank you in advance.
Edit: I've found my solution and had to change something.
You can read it here starting from Edit 2.
http://forum.xda-developers.com/showpost.php?p=68632922&postcount=84