please help - Motorola Atrix HD

i have an att atrix hd and i installed the safestrap and since then decided it wasn't for me as of yet... i deleted the partition in slot1 NOT the stock and when i rebooted my phone i now only have 4 and some change gig instead of the 8 i had before.... please... i am begging.... how do i get my memory back? i flashed it with the flash and root and etc. that the myth team came up with and to no avail. i dont know where to post my question and i need the memory back badly. this is internal memory we are talking about and not external.. I just flashed the aokp_mb886_unofficial_2013-05-08
but still same issue..

im no expert
Hi there, other than my "Hello" post this is first, but maybe others will chime in. I used and screwed up my AHD with safestrap too, was all my fault, i believe it's a good tool.I too had lost memory, i believe it was something to do with the original stock partition, long story short, over a few weeks i really messed it up. Thanks to a lot of folks on this site, and LOTS of reading, i believe i finally got it right, so, here goes.....
First, I believe, again I'm no expert, that the Mythtools is for loading stock roms, i don't know if its ok for customs, but thats not the issue. Second, before I loaded my stock rom, which I got here, and made sure I had the latest drivers installed, if you've been messing around you should know how to do that.
Third, I made sure there was nothing on the phone i couldn't live without, because it was all going by by.....
Forth, I used option #1 in mythtools, when finished i booted into recovery.
Fifth, in recovery, (not safestrap, it is CMD), i used every wipe and format option available.
Sixth, I ran option #2 in Mythtools (to the letter) and installed my factory ROM
After that I re-rooted, re-unlocked the bootloader and had to fix fastboot, was stuck and not booting normaly, i found info here, http://forum.xda-developers.com/showthread.php?t=2260105,
......installed all my tools, ROM manager, TiBU, etc. and.......
MADE A RECOVERY FILE
I hope I helped, this place has helped me alot, like I said, maybe an expert will chime in.
One more thing, I bought a new phone before attempting, was silly, wasn't too hard

I already answered this in your other post.. Did it not work?
Sent from my PACMAN MATRIX HD MAXX

I did the same thing and i installed stock with the same prog you used...
when i get stock up and running it says i have almost 5 gig but when i boot into recovery it says i have emmc or whatever of 8 gig... but when i boot it says my tot space of 4.86
i appreciate your response though... i really do....
i dont know what i have done... i am using cwm recovery now and i am just at wits end
please.... anyone...

Use rsd and flash back to stock.
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
Use rsd and flash back to stock.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
When I do that it gives the error due to it being partition incorrect.

I'm pretty sure that that is 4.86 USEABLE gigs not total. 8GB is just an estimate. Formatted space is less and the OS also makes it less
Sent from my MB886 using xda premium

Related

RAZR recovery on Droid 4?

Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
jgardner said:
Anyone tried using the RAZR recovery on the Droid 4? Lookin to do up the Arctic rom, but would feel much better if I could get a nandroid.
EDIT: This is the link to the RAZR recovery I was mainly thinking of: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Why not do the nandroid with safestrap?
I didn't think safestrap was working with the D4?
jgardner said:
I didn't think safestrap was working with the D4?
Click to expand...
Click to collapse
I dont know whats going on lol.....everyone is coming with all these different stories. I used the root exploit that was out and used the safestrap for recovery. I dont think I did anything different than anyone else. And then i took a chance flashing a Razr rom
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
jgardner said:
Oh yeah, the original utility had the safestrap didn't it? The latest utility doesn't anymore (although I think it works).
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I took it out until Hashcode brings it out for Droid 4. I've been corresponding with him and if the maker of Safestrap tells you it isn't safe to use on Droid 4 yet then you usually should listen.
All up to your risk though.
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
mattlgroff said:
Not yet. There is a reason we have warnings on these...
I hope we get fastboot yet. You cannot just "make them" they have to be leaked.
FYI Motorola does Fastboot files, not SBF now.
Click to expand...
Click to collapse
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
---------- Post added at 02:27 AM ---------- Previous post was at 02:24 AM ----------
As far as the warnings i didnt see the warning to not use safestrap till i got on here and it was to late. I figured since i was able to boot into recovery and make a backup i would be ok
Briteyez83 said:
Im new to root even though i have learned pretty quick. Finally after much pain and suffering got my X's bootloader unlocked and rooted some time in Nov. What does leaked mean and what is the difference between fastboot files and sbf?
Click to expand...
Click to collapse
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Briteyez83 said:
I made a nandroid using safestrap, or thought i did. I made my backup so i figured i would try that arctic rom so i followed the directions step by step. After i wiped cache and factory reset i went install from sd and the arctic rom that i know i put on it was not there. So i figured i would flash back to the backup i just made and try the process of putting the arctic on my sd. Some how i ended up bricking my phone and am now stuck in bootloader and my device is looked. Have you or anyone else made an sbf, oneclick recovery or a way to unbrick my D4?
Click to expand...
Click to collapse
Which FASTBOOT error are you seeing? It should be referencing one of the partitions.
Sent from my DROID4 using XDA App
greekchampion04 said:
You would be Man of the Year if you did that. You mean you bootstrapped it, right?
Leaked means they have to trickle out from Motorola/Verizon somehow.. either on purpose or by "accident" somebody on the inside putting them out there for use by our wonderful devs.
As for SBF vs fasboot, i dont know exactly the difference but think of them as different types of "recovery" that can be used to fully restore your phone to factory condition.
Click to expand...
Click to collapse
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Briteyez83 said:
Yes, i mean bootstrapped and you mean woman of the year, right? My bf said the difference between the two is SBF your makinga mirror image of everything and doing a complete system dump and fastboot is just cutting the power for a split sec. It will clear your immediate cache but some memory is still there.
Click to expand...
Click to collapse
I cant help unless I know what your error message says when you turn on the phone. :/
Sent from my DROID4 using XDA App
Send me your email addy in a message and ill send you a pic of it
Briteyez83 said:
Send me your email addy in a message and ill send you a pic of it
Click to expand...
Click to collapse
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Hashcode said:
Ok, so it's WEBTOP that is behaving badly.
Let me see if I can get an RSD Lite file for you to try. Do you know how to use that?
Click to expand...
Click to collapse
No, i dont. Im new to root, just rooted in nov. If you give me something thst would fix it that would be awesome.
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Hashcode said:
Unfortunately, the fix isn't exactly a simple one.
It comes in 3 parts (assuming you're on Windows):
1. You'll need to download and install RSD Lite which is what is used to flash the fastboot restore files from Motorola:
http://dev-host.org/ug07spima1mq/RSDLite5.5.rar
2. Download and install the Motorola USB drivers to recognize your phone in fastboot mode:
http://www.mediafire.com/?z5qpc8v3xza25e6
3. I'm setting up a mini WEBTOP fastboot restore file based on the latest RAZR fastboot files (I say small.. but it's still quite a large download). The version is slightly off from the D4's but it might be close enough, and I think it's worth a shot:
[ Getting this file setup will take me about an hour, but you can get steps 1 and 2 ready for now ]
ALSO KEEP THE PHONE POWERED OFF FOR NOW TO SAVE BATTERY. FASTBOOT WILL NOT PROGRAM WITH A LOW BATTERY.
Click to expand...
Click to collapse
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Briteyez83 said:
Thank you so much. My bf is leaving his laptop here so that i can do this since he is building the main cpu right now. Ill makev sure i let you know if this works or not after ive finished. I was going to have verizon send me a new one since i just bought my D4 on the 17th and i have 14 days. But i just dont want to risk my warrenty getting voided. Once again thank you.
Click to expand...
Click to collapse
If it works, I'll create a new thread with the instructions as I believe there are a few in your situation.
Yes there is quite a few. Ill let you know as soon as i can

I'd like to root but.. I need advice on whether or not I should

As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? I got confused with that.
Afterwards, I dl safestrap once I'm rooted? or should I just dl it and put it onto my phone all at once?
Apologies for the noobness. I'd rather be a noob asking questions than a retard who goes ahead and does things and finds out he screwed up too late.
Rooting is done to get superuser permissions within Android so you can install some advanced apps and modify system files which can all be done from within the stock ROM. Rooting then flashing an unofficial ROM is a little more advanced and something I haven't done yet so I can't help you much there. I'm waiting for something a little more stable since my Droid 3 is my main phone. You can read Hash of Codes site (the developer of ICS/JB for the Droid 3) on how to safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
To root use Motofail. I know it says its for the Droid 4 but the original Droid 3 root exploit was patched with the latest OTA so we have to use the Droid 4 method called Motofail:
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
DróidScìon said:
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
.
Click to expand...
Click to collapse
My D3 has Maverick as non-safe for daily driver and the latest Hashcode for fun. I find that to be the best combination. Once Hash finishes the camera and JB is working reasonable well, JB will be my DD.
I also have an SGS3, TF300T, and a Spica, all of them rooted.
once rooted, make sure you use safe strap. It makes roms easy to try out before having to settle
Sent from my DROID3 using Tapatalk
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
DróidScìon said:
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
Click to expand...
Click to collapse
Safestrap 1.08 is the 'normal' ssafestrap
Safestrap 1.08e/f/g is an advanced safestrap with extra features like touch etc but not by hashcode
Safestrap 2.10 is the latest which allows the new kernel with the kexec ICS/JB to be used.
2.10 It appears to also work fine with normal roms so i'd use that
DróidScìon said:
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? .
Click to expand...
Click to collapse
If you were stock 906, there was no reason to run the 1-click.exe - that's only for people who rooted their phones and deleted bloatware to get the phone back to stock, or people whose phones are bricked somehow. Coming from stock, just running Motofail was enough to root.
I will concur with everyone here that running rooting, installing and running Safestrap, and installing a custom ROM - and leaving your rooted stock alone - is the best way to go. It will be a lot easier to unroot later on if you want to sell the phone, etc.
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It doesn't matter. Choose which has enough space.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It's asking where to backup TO, like the post above me, choose wherever has space. Backups are about 1GB. You may wish to move it to your computer after if you don't have much space on your device. You can always stick it back on your external sd via card reader if needed, but it's really hard to brick while using safestrap
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Sent from my XT860 using xda premium
I saw that, and before I rooted, I did a Factory Reset on the phone and formatted my SD card. So I have 11+gig free on Internal and 15+gigs on External.
Now, I just need to learn to Flash RoMs (probably more to it than just hitting a button that says flash .zip) and find some info on the "must-have" apps for a rooted phone.
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
DróidScìon said:
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
Click to expand...
Click to collapse
If your contacts are on your google account they will show up.
What other account info do you mean?
You should go ahead and restore contacts. just go to Settings>Accounts and Sync>Google, then turn contacts sync on.
Endoroid said:
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Click to expand...
Click to collapse
I must have made another noob mistake. Everything went well, up until my first startup with the new OS (cyanogenmod9). It has been at the startup screen for over 15minutes right now. I must say, it is one awesome startup screen, with the blue effects and all, but I would love to get to the desktop/homescreen, haha.
If you guys have any advice I would greatly appreciate it. This is a Droid 3, it was rooted a couple hours ago, I did the safestrap as described, created a backup file, etc. My only guess is I jumped the gun by trying this OS on my Droid3 and it may still be under development? FWIW to you, this is the first I've rooted or modded a smartphone in my life, from 0-full speed in a couple hours is what I was shooting for using everyone elses experience.
thanks
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Phibernaut said:
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
thanks. since my last post I used a more detailed how-to, and wiped 3 different areas for data. Now, i had only a black screen (with power, barely lit) and it never even got to the cool blue screen.
I'm currently in safestrap after pulling my battery again, just trying to figure out how to revert back to my standard OS (rooted) and try a ROM like MavRom since it's suppoedly fully capable and stable. I'd love ICS, but I just want a working phone right now
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
good news is, I did enough steps correctly, that I was able to startup in my unsafe mode, and my normal rooted system is functioning fine. That makes me very happy.
This duel boot thing is pretty cool, reminds me of having bootable thumb drives on my old linux system with different OS's. I hope i can get a seperate OS working, however, that fits my needs for a day to day functional phone, without all of Verizon's crap on it
Once rooted use titanium backup to back up apps and data.
Only restore with the same ROM though, the following is in increasing order of risk
restore app only to exact same ROM+version
restore app+data to same ROM+ver
restore app only to update of same ROM
restore app+data to updated ROM version
play chicken with a bus on a highway
restore apps to different kernel e.g. CM7 backup => restore to CM9
check to see what a gun firing looks like down the barrel
restore app+data to different kernel
restore app+data to an older ROM or kernel
do anything at all with system apps+data if you don't know what you're doing

[Q] KF7" Refuses to boot past "Blue" Logo

Hello, I have a Kindle Fire HD 7" running the downgraded 7.2.3 from KFFA. Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo.
My screen doesn't do the "White haze" that others have mentioned.
Still boots into recovery allowing for wipes + installs.
I have reverted back to 100% stock then made my way back to stock + TWRP three times now, and have looked rather extensively through any threads even somewhat relative to my own problem.
I've been using the Factory fastboot cable to get into fastboot if that makes any difference.
I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before.
ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)
Have tried my cable from my Note 2, Captivate, Epic 4G Touch, and stock KFHD 7" cable as well as the factory fastboot cable.
Kinda stuck, have gone round like this for about 4 hours + now and I must say, the KFHD 7" has been the biggest pain out of any of my Androids by far xD Great tab though.
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
If I left out anything, please, let me know and I will respond ASAP.
veladem said:
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
Click to expand...
Click to collapse
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation said:
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
veladem said:
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
Click to expand...
Click to collapse
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
LinearEquation said:
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
Click to expand...
Click to collapse
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
veladem said:
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
Click to expand...
Click to collapse
You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS. Just drag and drop ROM onto internal SD card before booting into TWRP.
LinearEquation said:
You never said you could access an OS. You simply said you could not get past TWRP. You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS.
Click to expand...
Click to collapse
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
veladem said:
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
Click to expand...
Click to collapse
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
LinearEquation said:
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
Click to expand...
Click to collapse
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
veladem said:
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
Click to expand...
Click to collapse
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
LinearEquation said:
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
Click to expand...
Click to collapse
I give back to the community by offering free Android and iPhone modding in my area, and free support via text and email.
Plus I make sure to tell them to check out the Dev's thread or website and to consider donating to the people who make the magic happen.
The only service I make people pay for is electronic repairs which is a flat rate of $20 + customer buys the parts.
So I think I give back to the community at least a little seeing as I have at the least 20+ people a month asking for help cause some idiot installed a unstable ROM on their phone and 4G vanished or other problems.
By the way, since we are laying our d*cks on the table, might I add that boasting about how many "Likes" you have or "Thanks" isn't something to be proud of, you earned them yes, but don't shove that in other peoples faces, that's just childish.
Thanks again for trying to help.
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did try that yes.
Thank you for helping btw.
It's water under the bridge for me. Would be funny if that were the case though because asking him if he swiped was one of my initial responses to him.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes sir I did.
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Sucess! Kinda :/
stunts513 said:
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did verify that it is on stock, rooted, de-self updater-ed, 7.2.3. It was on 7.3 something originally.
Hellfire flashed over just fine, CM 10.1 (I think) Flashed it, booted KindleFire (Orange) then (Blue) then Boot logo Booted pretty fast too.
mrkhigh said:
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, 2012 KFHD 7" (Tate)
Yes, TWRP works fine.
No, I got Hellfire to flash, but so far nothing else will flash 0.o :/
Also, I did all my restores from KFFA, BUT, I did do a original backup via ADB and did a restore via Fastboot thinking it might have been KFFA but no go still.
And yes, the thread kinda goes to poop cause I was already kinda upset cause this has been the most frastrating Android to work with, and then the pressure got compounded just cause I decided to ask for help :/
If any of this info helps, please let me know, I believe Hellfire is CM 10.1 . . . I believe, that's off the top of my head though.
Thanks!
To be honest I've only installed kinology... Wife won't let me get rid of the kindle os. I didn't really needed kinology but I wanted to update and did not want to reset it up again. He basically ran a neater version of what I was doing.
Is there an error when you flash the ROM and what ROM are you flashing
Sent from my XT907 using xda app-developers app

Flash back to stock and leave it

I'm probably not going to get an answer, but I'm going to ask anyway. My wife's phone was running an old version of CM, I can't remember which one it was though. But anyway, it was running like crap. She would tap an icon and it would take forever to load the app or it would just freeze totally.
So I thought about it and installed safestrap on it and flashed CM12 to slot 1. I guess I flashed the other older rom to the stock slot. I don't know how I did that, I thought only stock goes there. It's been a long long time since I messed with her phone.
So now she has the first crap rom on the stock slot and CM12 on slot 1. The problem now, is that CM12 runs like crap on her phone too. It's like old people screwing in molasses.
My question now, is do I just find the original stock rom and flash it to the stock slot? It won't let me wipe the data from the stock slot, so I guess I have to dirty flash the stock rom over top of it. Is that a good idea? And also, where do I find the correct stock rom to install? It's pretty old and I don't know what the last known stock rom for it is called or where to find it.
She's stuck to this phone for sentimental reasons, she won't give it up. I'd at least like to make it run smooth again. If anyone helps me with getting her phone back to normal, I would truly appreciate it.
Thank you.
You could find an fxz file for jellybean it's like 98.2 or something boot into fastboot and use red lite to flash the fxz, that would put you back to stock, then if you look in the razor droid section they have one click root that works for our phone too I believe, then you can reinstall safestrap and have it back to normal,
Also speeds can decrease with your older sdcard if the ROM slot is on SD are, I am not sure if its on emmc or sdcard but if it is on sdcard it could slow down as the card has aged, better cards faster read
I
thanks for the response. I just found Blur_Version.5.9.905.XT875.Verizon.en.US(67246). move this zip over to my external card and then boot into recovery. I was then going to delete slot 1 and flash this rom into the stock slot. Would this work?
It all depends what boot loader your on, if you are on the new safestrap 3.7 no it won't work, if your on old like 2 something or gingerbread still it will, but if you flash a ROM from before jellybean and updated to jellybean you will have to use fastboot to flash no !after what, most people would call it a BRI l cause they can't figure out how to use rsdlite and fast lot, and it probably won't work because you need to flash that using rd
Sdlite
1. Google rsdlite fastboot flash tool
2. Google droid bionic jellybean fxz file
3. Download both files and programs
4 place a working folder on your desktop
5. Turn droid bionic on if fuilly charged into fastboot mode with power + down I believe, might be power plus + volume up and down, might be power plus volu!e+ up you can google that to how to boot into bionic fastboot
6. Once bionic is booted into fastboot and you have the fxz file and rsdlite open rsdlite
Make sure your bionic is connected to your computer rsdlite will see its in fastboot mode, then you can flash the fxz
I would do so!e research how to do it before I did, I ha e flashed a lot of fxz but if your new you can mess up, with a bionic its almost impossible to brick it because it has fast lot and can flash an fxz, but still if you don't know what your doing you might give up trying to fix it.
There are some fxz out there made to not flash data, or have a fix for a cpommom error, when trying to flash fxz sometimes you get an error because of fb_mode_set and fb_mode_clear you have to google how to remove those lines if you get an error there is an fxz out there with those lines already removed you just gotta find it
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
OK, I will try what you said tomorrow. But for now though, do I just boot into safestrap and delete rom slot 1 and then shut the phone off? Then boot to fastboot like you said and flash Blur_Version.5.9.905.XT875.Verizon.en.US(67246) with rsdlite? It's been a while since I've done this, it's really hazy, but familiar. I appreciate you taking the time to help me out with this. Thank you very much.
DroidisLINUX said:
You could find an fxz file for jellybean it's like 98.2 or something boot into fastboot and use red lite to flash the fxz, that would put you back to stock, then if you look in the razor droid section they have one click root that works for our phone too I believe, then you can reinstall safestrap and have it back to normal,
Also speeds can decrease with your older sdcard if the ROM slot is on SD are, I am not sure if its on emmc or sdcard but if it is on sdcard it could slow down as the card has aged, better cards faster read
I
Click to expand...
Click to collapse
I got around to reflashing it to day, worked great, just had to edit 2 lines in the .xml of my rom, but it worked great. would you mind pointing me in the direction of the razr one click root? all I'm seeing is install a virtual machine on my pc, I did that before I remember, but if there's an app I can install to the phone and it would do everything, that would be great. thanks for all the help.
Its in the razor forum moto razor one click root Google should find it, or look threw xda razor forum for it, it should work on bionic if not then use the virtual box tiny Linux install methld
Sent from my DROID BIONIC using XDA Free mobile app
DroidisLINUX said:
Its in the razor forum moto razor one click root Google should find it, or look threw xda razor forum for it, it should work on bionic if not then use the virtual box tiny Linux install methld
Sent from my DROID BIONIC using XDA Free mobile app
Click to expand...
Click to collapse
I don't think that first one you mentioned works for the bionic. However, the virtual machine does work and saferoot also works.

messed up my bionic

Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
rp201 said:
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
Click to expand...
Click to collapse
Howdy! Sorry it's taken three months for your question to get any attention. Bionic forum's pretty dead, eh? I'm amazed it's still an officially supported Lineage device. Go team!
Sadly, the no one ever found a bootloader unlock, as a fellow informed me here two years ago. Unless some clever hacker happens upon a Bionic and decides to crack it for kicks, it's not likely to happen. But at least we have SafeStrap and Lineage!
You may know this already, but you didn't mention it in your post, so I'll go ahead and say: when installing a ROM like Lineage on the Bionic with SafeStrap, you need to install it on ROM Slot 1, not the Stock ROM Slot. I imagine that might be why you bricked your phone (I've done it myself a few times too ).
Now that I've given you the skinny on the Bionic's limitations, let's see if we can't get you back afloat. Whenever I bricked mine, I never used RDS Lite—I found a utility called House of Moto. You can find the home page here, but you'll need to create an account to see the important stuff and the downloads (you'll also need to install Java). But if you're more familiar with RDS Lite, feel free to use that instead
System images for the Bionic are hard to find nowadays. I seem to have found one link to an article with a direct download link to an update file at the bottom, which I'll link to here. Whether the update file is the same as an FXZ file RDS Lite/House of Moto requires, I'm not sure. Give it a try and see how it goes! If not, I may have a copy of the file on my old computer at my parents' house. If the linked update file doesn't work, I'll see if I can't get ahold of my image file.
Finally, if you do happen to get things up and running happily, I've got a list of optimizations that help Lineage run more smoothly.
Best of luck! :good:

Categories

Resources