[GUIDE] Restoring Your KF to stock from ROMs - Kindle Fire Android Development

Here's how to restore your KF to stock from a custom ROM
make sure you have the stock recovery installed (if you are in CM7 you are)
First, download the latest official update from here -> http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620
then download this file -> http://www.mediafire.com/?31sljwzyu0i1nev
and place it on your sdcard
it should be /sdcard/command
rename the amazon update to update.zip (even if it's a .bin file, make sure it is update.zip, NOT update.zip.bin
then, place that file on the sdcard under /sdcard/kindleupdates/
it should be /sdcard/kindleupdates/update.zip
turn off usb mass storage mode
go into the adb shell and type
cd cache
mkdir recovery
cp /sdcard/command /cache/recovery/
idme bootmode 0x5001
reboot
i just went from cm7 to stock and it worked fine

<3 thanks man

This makes me much more inclined to try to CM7; however, I think I will wait for a final version of the ROM. Seems like a lot of good progress is being made. Thanks for posting!

lol stick to stock until the wrinkles are ironed out. i feel like everybody wants in on the alpha builds for all devices until they actually test it out and wanna go back

JackpotClavin said:
lol stick to stock until the wrinkles are ironed out. i feel like everybody wants in on the alpha builds for all devices until they actually test it out and wanna go back
Click to expand...
Click to collapse
That's the truth. When I get payed Friday you got your self some beer money coming.
Sent from my Kindle Fire using xda premium

All in favor of from now spelling paid as payed say I
I always make that mistake, we should have the option to spell it both ways
Sent from my DROID Pro using XDA App

I think the current CM7 build is pretty soild.
Is it possible to mess around with ROMs in Eclipse or do you need to be running linux?

Never tried using another OS. I believe the easiest OS to set up a build environment is linux (ubuntu primarily)
Sent from my DROID Pro using XDA App

So has anybody actually done this?
Sent from my DROID Pro using XDA App

JackpotClavin said:
So has anybody actually done this?
Sent from my DROID Pro using XDA App
Click to expand...
Click to collapse
I tested it. It worked for me. I went back to cm7 tho.
Sent from my Kindle Fire using xda premium

Sweet, I feared I might've skipped a small step or made a typo thanks!
Sent from my DROID Pro using XDA App

Ahh see now I can take a dip into the CM waters.

Tnis is impossible if adb shell don't work and device have bootloop?

animefun135 said:
Tnis is impossible if adb shell don't work and device have bootloop?
Click to expand...
Click to collapse
Maybe try to explain in better English
Sent from my Kindle Fire using xda premium

This is impossible as long as my device is infinitely restarts after logo Kindl Fire ...
Just does not work command adb shell.
This method is useless if the command adb shell is broken.

I don't think it was meant to provide a way out in case something gets messed up, just a way to get back to stock should you want to under normal circumstances.

animefun135 said:
This is impossible as long as my device is infinitely restarts after logo Kindl Fire ...
Just does not work command adb shell.
This method is useless if the command adb shell is broken.
Click to expand...
Click to collapse
Sure, it doesn't work, since you jumped the gun and tried to do this on your own without waiting for someone knowledgeable to put out clear instructions.
Any other posts people put up probably won't apply to you because you jacked up your Fire.
Why not seal deal the go for the coup de grace and make a factory cable, that forces it into fastboot etc so you can try and get back into adb.

Thelgow said:
Sure, it doesn't work, since you jumped the gun and tried to do this on your own without waiting for someone knowledgeable to put out clear instructions.
Any other posts people put up probably won't apply to you because you jacked up your Fire.
Why not seal deal the go for the coup de grace and make a factory cable, that forces it into fastboot etc so you can try and get back into adb.
Click to expand...
Click to collapse
This is the best post of all time since I broke my Kindlе. I'll try it if it is not repaired at a service center.

Not sure if that's sarcasm. Note: the bulletproof vest goes on before you get shot, not after.

Thelgow said:
Not sure if that's sarcasm.
Click to expand...
Click to collapse
Well, that was the first real piece of advice he got... So I suspect that he might actually be trying to say 'thank you'

Related

Fresh 0.3 Reboot

Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
l3l2ad said:
Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
Click to expand...
Click to collapse
what commands did you use...? nothing in customizing bootscreen should damage anything on your phone...?
Last resort = RUU back to stock re-root and reflash..
So why did you feel you needed to make a new thread about this instead of just posting in the thread itself which is already dedicated to the rom and issues...
... ?
Tenny said:
So why did you feel you needed to make a new thread about this instead of just posting in the thread itself which is already dedicated to the rom and issues...
Click to expand...
Click to collapse
because it would get buried and no one would read it for days... hes hoping this way to get a speedy answer... im sure if you felt like you screwed up your phone somehow you'd be clicking on new thread to get as much help, as soon as possible... ???
if you cant help or are willing to help stop cluttering the forums with your "forum police" attitude...
i'm not going to answer your question specifically BECAUSE you made a new thread instead of posting in the existing one.
l3l2ad said:
Got a slight issue...flashed system fine and messed up trying to customize my bootscreen...anytime I try to mount as a disk drive the phone freezes then reboots.
Only thing I can think of is the 'mount' command in shell. Didn't mean to run the command, but I did. Is there an easy way to fix this?!
I've tried re-flashing the ROM and fixin the permission...neither worked.
Click to expand...
Click to collapse
wipe everything then try to reflash.
wrx4memp said:
what commands did you use...? nothing in customizing bootscreen should damage anything on your phone...?
Last resort = RUU back to stock re-root and reflash..
Click to expand...
Click to collapse
I used the 'mount' command while in shell.
Thanks for the help even though I posted WRONG.
I got my issue fixed by using a nAndroid backup..retsored and th issue was gone. I'm thinking the problem happened because I didn't have the droid SDK on my PC..fixed that too!
haha. mount by itself only displays the current mounted volumes. there isn't anything you can do with mount alone in order to render your system unusable.
-------------------------------------
Sent via the XDA Tapatalk App
geekykid said:
haha. mount by itself only displays the current mounted volumes. there isn't anything you can do with mount alone in order to render your system unusable.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Thanks for the info...well im not sure what happened then LOL I'm tryin to teach myself so go easy on me

[ROM] CM7 for the Kindle Fire

Howdy everybody! I just got CM7 to boot for the first time on the Kindle Fire. As of right now, I believe the touch screen is off 90 degrees. I know there's a fix in the source code, I just forgot where it is but I'll look. It might actually be an edit to the build.prop. Pictures below:
http://i.imgur.com/SE4nx.jpg
http://i.imgur.com/8ZRCW.jpg
I'd really love to stay and chat, but I'm actually really late for work
More on this when I get off from work and before I gotta leave for school
12/4:
12/13
This ROM is obsolete; it was more of a proof of concept than an actual everyday ROM. It would suggest staying stock until ICS is ready and stable.
The ROM's update.zip
The KF's clockwork recovery to install files located under /sdcard/update.zip
The KF's stock recovery
md5sums
update.zip e0e8f8bb08318ef15c8afc042c2e9766 update.zip
updaterecovery.img 38eb5308439a6f1e256a4914ab06d508 updaterecovery.img
stockrecovery.img c4f028310bd112649c94be6a4171f652 stockrecovery.img
Make sure your battery is fully charged, rooted, you know your way around adb, and that your kindle fire actually connects to adb and works successfully before installing CM7. Installing CM7 will wipe your system, data, and cache, and I'm not responsible for any malfunctions :/ I've done this for versions 6.0 and 6.1, but I have not tested under 6.2
Copy the CM7 zip to the root of your sdcard, so it's /sdcard/update.zip, and copy the updaterecovery.img file to your sdcard so it's /sdcard/updaterecovery.img. For Clockwork, you will need two files to be present under /cache/recovery/ so copy these two files to your sdcard log last_log. You'll need to copy them to the root of the sdcard as well. Before proceeding, I highly recommend you go into adb and verify the md5sums of the two files you just put there. If you aren't familiar with this, you need to unmount your kindle from the PC, type:
adb shell
cd sdcard
md5sum update.zip and make sure the numbers generated after a few seconds match the numbers posted above
md5sum updaterecovery.img and again, make sure the numbers generated after a few seconds match the numbers posted above
If these numbers don't match, I wouldn't proceed as your file might be corrupt, and I would try again
Now we will need to copy these two log files to your cache partition under /cache/recovery so type
adb shell
cd cache
mkdir recovery
cd /
cp /sdcard/log /cache/recovery/
cp /sdcard/last_log /cache/recovery/
If your files are verified to be okay via the md5sums before, we can flash clockwork now, by typing
adb shell
dd if=/sdcard/updaterecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Now, we can reboot recovery by typing "idme bootmode 0x5001"
If it says the bootmode has written, you can type reboot and it'll reboot
I install all of my zips without removing the usb plug from the computer or the kindle and I have never failed once, I don't think I've ever tried it without doing so, but if you don't wanna mess with success, don't remove the usb cord. I'm not saying anything bad will happen because I've never done it, but I'm just saying I'm batting 1.000 without removing the usb cord
Now that you're in clockwork, look below the menu to see if there are any error messages written in white. If you see one about something being read-only, that's fine. If it complains about log and last_log, you might've missed a step above. If you see an error that I haven't mentioned, and you would like to reflash the stock recovery and reboot like none of this ever happened, skip to the bottom.
About Clockwork: since we can't navigate to items in Clockwork, we have to bring the items to us. Basically what I did was I shifted the entries of Clockwork so the "Install update.zip from sdcard" was listed first, not the Reboot system now option. That way, we can just press OK (The power button) and it'll install the CM zip. I also changed it so you don't have to scroll all the way down to the "Yes" option to confirm install as I pushed that to the top also so we can just press OK. In the update.zip I included the wiping of system, data, and cache because we can't navigate to mounts and storage to wipe those things in Clockwork, so we have to do it automagically.
In the clockwork that I made for you, all you have to do is press the power button a bunch of times. There will be a point there you have to scroll down to "Yes", but you can't, that's fine, just press OK, even though it says "No" it will mimic you pressing Yes.
After you press the power button 3 or 4 times, it will being the installation. Give it a minute or so, it will install
After installation, we will need to reflash the stock recovery to your kindle. Type adb shell
mount sdcard
exit (this will bring you back to the non-shell command line)
then adb push /sbin/
So for me, (I use linux) I use adb push /home/jonathan/kf/stockrecovery.img /sbin/ **there's a space after .img and /sbin/**
Then type "dd if=/sbin/stockrecovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery" it will say something about 16 megs written or something. Once that happens, type adb reboot or reboot and your kindle will reboot. Actually it will reboot twice. Give the initial boot a few minutes, and the CM7 boot logo will appear
Congrats Calvin!!! Awesome!
The only thing that tempers my excitement about this or CM9 is wondering what happens to Amazon's apps once we install a CM build of Android.
Will the Kindle still see Amazon and Visa Versa as a registered Kindle owner
Will the Amazon video app still be installable and usable (albeit we have to unroot?)
Re: Above...can CM be unrooted after installed?
Basically, I just want to know what I'm LOSING by going to CM on the Kindle Fire.
good job!
do the apps and wifi work?
tck9223 said:
good job!
do the apps and wifi work?
Click to expand...
Click to collapse
http://i.imgur.com/8ZRCW.jpg - it looks like
I wasn't able to test much out because the screen and the touch sensor aren't in sync. Basically the screen is facing one way and the sensors think the screen is oriented 90 degrees in another direction. There's a quick fix but I had to leave for work
I managed to open the wifi screen but couldn't click my ssid let alone type the password with the orientation/sensor hiccup
Sent from my DROID Pro using XDA App
rmagruder said:
The only thing that tempers my excitement about this or CM9 is wondering what happens to Amazon's apps once we install a CM build of Android.
Will the Kindle still see Amazon and Visa Versa as a registered Kindle owner
Will the Amazon video app still be installable and usable (albeit we have to unroot?)
Re: Above...can CM be unrooted after installed?
Basically, I just want to know what I'm LOSING by going to CM on the Kindle Fire.
Click to expand...
Click to collapse
I don't have all of the answers for sure but I think at this point no one really knows.
1. The device would no longer be registered as a Kindle if it is just stock CM. If you add the regular Kindle for Android app you wou still have access to kindle books but not other content.
2. The Amazon video app should work because it is reported as working on other unrooted devices. You should be able to unroot CM7(9) the same way that we currently unroot the KF. I suspect that it will not be long before we see a modified Kindle Video app that runs on rooted devices as I have noticed an increase in developer activity and interest in the device.
3. Yes
I too am concerned about these things as I have become very accustomed to instant video and all of the other features of the KF. I see many ways of having both. I suspect that once CM is fully operational we will have a zip that we can flash in recovery to add all of the Amazon apps the same way we do with gapps.
Suprising to see a ROM before a recovery.
Sent from my SPH-D710 using xda premium
Lol we have recovery. It's just ineffective
Sent from my DROID Pro using XDA App
pyrostic said:
Suprising to see a ROM before a recovery.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Very surprising but the recovery might be released before the ROM
The Fire is my first Android device and I have been following the XDA forums closely because this kind of hacking and tweaking is just WAY to cool.
Congrats on the CM7 boot. Can't wait to see more!
Got a donate button? I'll throw in for the hard work! Would love working CM7 or 9 on this guy.
SikYou said:
Very surprising but the recovery might be released before the ROM
Click to expand...
Click to collapse
You know something about TWRP I don't?
Sent from my SPH-D710 using xda premium
I know when its released loads of Rom development will follow.
pyrostic said:
You know something about TWRP I don't?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Probably not. I know that there is a working build though and that it has been said to be working great. I know there are still some hurdles but the guys are working hard
Sent from my Kindle Fire using Tapatalk
SikYou said:
Probably not. I know that there is a working build though and that it has been said to be working great. I know there are still some hurdles but the guys are working hard
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Talking about TWRP? if so what hurdles?
Sent from my SPH-D710 using xda premium
Well I flashed cm with clockwork. I'll post a zip and instructions later
Sent from my DROID Pro using XDA App
JackpotClavin said:
http://i.imgur.com/8ZRCW.jpg
Click to expand...
Click to collapse
Great news.
But I think the biggest shocker is why do you have your wifi set to WEP?
pyrostic said:
Talking about TWRP? if so what hurdles?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yes TWRP. I am not 100% sure what is holding up the release. Agrabren has TWRP working on the KF but says that it may be a week or 2 until it is ready for release, he is the only one that knows for sure still needs to be done. I think 1 problem is lack of an easy way to boot in to recovery. Either way, looks like we aren't far off.
Sent from my Kindle Fire using Tapatalk
JackpotClavin said:
Howdy everybody! I just got CM7 to boot for the first time on the Kindle Fire. As of right now, I believe the touch screen is off 90 degrees. I know there's a fix in the source code, I just forgot where it is but I'll look. It might actually be an edit to the build.prop. Pictures below:
http://i.imgur.com/SE4nx.jpg
http://i.imgur.com/8ZRCW.jpg
I'd really love to stay and chat, but I'm actually really late for work
More on this when I get off from work and before I gotta leave for school
Click to expand...
Click to collapse
Congrats! Do you have a github repository somewhere that you've got your code committed that we can look at? I do CM7 for the Samsung phones (Galaxy S and Galaxy SII), and so I'm interested in putting Ice Cream Sandwich on the Fire but haven't got around to doing anything on my Kindle because I've been busy the ICS for the phones. Starting with what you've got would be a good start and then I can try to put ICS on it.

Help, Flashing Image from Ubuntu to Stock!

Noob here... I just installed Ubuntu to see what all the hype is all about. I had no problems flashing, however I found it toooo laggy and unstable and I decided to go back to stock. There is one problem, i forgot to back up google factory images. I need to put the images in the root to flash, but i have no way putting them on because my Mac computer doesn't recognize my Ubuntu Nexus. Any Ideas guy, need some big help
Well yet another one of these. There's this thing called Google. I don't know if you ever heard of it. Ask there and you might get an answer. Google also has a friend called YouTube if reading seems to hard for you.
Sent from my Galaxy Nexus using xda premium
I can't find anything in my situation.. Why comment, if your not going to help in the first place.
you dont put images in root to flash...
use fastboot
calling yourself a noob doesnt absolve you from doing some basic research and reading.
Pirateghost said:
you dont put images in root to flash...
use fastboot
calling yourself a noob doesnt absolve you from doing some basic research and reading.
Click to expand...
Click to collapse
I guess I'm not explaining it right. I no longer have the Factory Image on my phone, I'm currently running on Ubuntu. My PC nor Mac could recognize the device, so fastboot wont work. I am looking for way to flash the image, that doesn't involve me downloading Ubuntu OS on my PC.
you dont understand.
YOU DO NOT PUT .IMG FILES DIRECTLY ON THE DEVICE
you flash them in FASTBOOT mode, which has NOTHING to do with UBUNTU
pretend you flashed a broken rom. GO BACK TO STOCK, none of this actually has anything to do with ubuntu
Man so hard the longest minute of my life. But finally found it. https://www.youtube.com/watch?v=QZcSC_MHkl0&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Man so hard the longest minute of my life. But finally found it. https://www.youtube.com/watch?v=QZcSC_MHkl0&feature=youtube_gdata_player
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
watch out, that spoon might come back tarnished....
Pirateghost said:
watch out, that spoon might come back tarnished....
Click to expand...
Click to collapse
Haha I know right.
Sent from my Galaxy Nexus using xda premium
Esteway.619 said:
Haha I know right.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
he should still be able to get into the bootloader manually...
Not only do Ubuntu have a guide on how to get back to Android but there is a nice thread in General which is called (funnily enough) 'How to get back to stock' - read that
What this clearly highlights is the fact you didn't read the official flashing guidelines as provided by Ubuntu

How to Unbrick a Hard Brcicked T-Mobile Note 3 SM-N900T

This is how I un-hard bricked a T-Mobile Note 3 SM-N900T
Part 1: What you need
A SD Card that is the Same Size as your Phone's internal memory. Mine was 32GB and I used it.
The unbrick image which can be found here: mega.co.nz/#!wxZh3CwR!UU1OBBAHACKHEO0eMK4crHBjKXUKJ7y8-vqjkQGzsMY
A program to put the image on a SD Card which is here for windows users: sourceforge.net/projects/win32diskimager
The Stock ROM. I got mine here. samsung-updates.com/device/?id=SM-N900T
ODIN 3.04 (this is what I used): mega.co.nz/#!xw4FHBzD!Zw9EMltI0g5AZYspg8aM6hFSXJFiiwCRORMqxoandW8
Part 2: Prep
Get the battery charged to 100%.
Find a PC and plug the powercord (microUSB Cord) directly into the motherboard. NOT ANY OTHER PORT.
Format the SD Card to ExFAT you need from Part 1.1.
Using the #3 Program from Part 1.3, burn the image to the SD Card. Its simple.
Part 3: Turn it on
Put the battery into the phone.
Plug the charging cord into the phone.
Put the phone into download mode by holding: <Volume Down> + <Home Button> + <Power>
Once you are in download mode press <Volume Up> to enter download mode. Now go to part 4
Part 4: Putting the ROM back on
Don't Deviate from anything here or do extras.
Open Odin from Part 1.5.
Press PDA and Select your STOCK ROM from Part 1.4
Wait a min for Odin to analyze the file.
Hit Start on Odin.
Part 5: How about someone get a MOD to fix the links in Part 1
How about someone get a MOD to fix the links in Part 1 as I was unable to link Properly. I am not going to do it because it pissed me off. :silly:
Notes:
Turn it on was just basic as can be, It just popped right on. Per the USB Ports I did use a USB-3 Ports on the back of my machine. I am not sure if that would make a difference or not.
Credits:
Credits are due, but I need to research who to credit again... It is Christmas Eve, and I am going drinking. I will do this on Monday when I get back to work.
So are these the instructions on the other thread I'd say is the original M
Sent from my SM-N900T using xda app-developers app
Thanks! Whats with the grey letterboxing? Thats probably killing your link. Glad the info on the thread helped you unbrick your device! Because when you pmed me asking me how to do it, I had no idea you already knew Until and if it is fixed, copy/paste works fine.
msmercy42 said:
Thanks! Whats with the grey letterboxing? Thats probably killing your link. Glad the info on the thread helped you unbrick your device! Because when you pmed me asking me how to do it, I had no idea you already knew Until and if it is fixed, copy/paste works fine.
Click to expand...
Click to collapse
system did it automatically. I have no clue why. I do like how it boxed out the parts.
and it is the why you do it from the other thread... I was asked to put links to what I used and how I did it. Nothing pisses me off more than having to dig through a thread looking for the solution. I just put it on top of a new thread. This way people don't have to dig. It does make sense if you think about it.
Imagine how much digging I had to do about two months ago when it seemed like I was the only person in this forum asking about it. Reading the pages in the thread I created answers alot of questions, and has detailed information that could prevent future mistakes that could result in such. Also at the same time actually learning something about the way file system repair and recovery on android can work.
It's all in the way you look at it. I'd open a bag of chips, crack open a beer, and read the whole thing - especially if I could learn new things - no matter how experienced I am.
chuko303 said:
So are these the instructions on the other thread I'd say is the original M
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
These are the steps zinnium took in order to get his to work, but the other thread is the original.
The other thread was pieced together from over a month of research and trial/error. We tried several methods, dug up some secret Samsung documents (credit given to those provided), and then came up with the OP solution by finally piecing some things from the sgs3, sm-n900a, and help from some experienced devs.
The important thing is though, that the method works.
Anyway, @OP, the image I have on media fire seems to download better. Take that link from the other thread and post here. MEGA sucks donkey balls IMO. There servers are slow, and always makes you wait forever.
ive never heard of anyone needing to connect the device before it would sdboot, so the following steps arent needed:
Find a PC and plug the powercord (microUSB Cord) directly into the motherboard. NOT ANY OTHER PORT.
Format the SD Card to ExFAT you need from Part 1.1.
Click to expand...
Click to collapse
HOLY S#!T, That's LEGIT!
A-effin'-MAZING!! I CAN'T THANK YOU ALL ENOUGH!
I CAN'T BELIEVE THAT WORKED!
I couldn't resist recording my first attempt. BOY I WAS SURPRISED!!
*For The Record; Shabby is correct, you don't have to be plugged into any external power source, for this to work...
**ALSO!; The Stock ROM may not always be needed, depending on the individual and their case's circumstances...
I've had ppl tell me that no matter what, they try turning on their phone(SGN2/SGN3/SGS4) and it automatically goes into download mode(without showing the warning screen)... So since it wouldn't boot system OR Recovery, I'd try Button-Combo into ODIN-mode, and press Volume-down at the warning screen, and system would boot!
I Had a hunch that might work in this case, and it DID! lol.
Now I'm just trying to put the unbrick.img onto the sdcard I wrote it to... I can't seem to get MTP up, through USB, though ADB works fine...
**EDIT: I forgot, that before I Bricked it, I had the USB settings to DM+MODEM+ADB, cause I WAS unlocking it...
(until a slip of a click and I wrote a backup of the NVdata to the EFS... =/ )
But, after I put the sdcard into my laptop, realized there's not nearly enough room to copy the .img to it...
***SO.... How am I supposed to be able to "dd if=/sdcard/unbrick.img of=/dev/mmcblk0 bs=1024 count=168960"?
I can't put the .img on the sd? Do I put it on the internal? or do I put it on another sdcard and put it in??
**** ACTUALLY, NVM.... THAT'S what I'm gonna do! XD ha
*****
[email protected]:/ # dd if=/storage/extSdCard/unbrick.img of=/dev/mmcblk0 bs=1024
count=168960
ck.img of=/dev/mmcblk0 bs=1024 count=168960 <
168960+0 records in
168960+0 records out
173015040 bytes transferred in 9.488 secs (18235143 bytes/sec)
[email protected]:/ #
=AWESOME!
M1k3Carson1369 said:
A-effin'-MAZING!! I CAN'T THANK YOU ALL ENOUGH!
I CAN'T BELIEVE THAT WORKED!
I couldn't resist recording my first attempt. BOY I WAS SURPRISED!!
*For The Record; Shabby is correct, you don't have to be plugged into any external power source, for this to work...
**ALSO!; The Stock ROM may not always be needed, depending on the individual and their case's circumstances...
I've had ppl tell me that no matter what, they try turning on their phone(SGN2/SGN3/SGS4) and it automatically goes into download mode(without showing the warning screen)... So since it wouldn't boot system OR Recovery, I'd try Button-Combo into ODIN-mode, and press Volume-down at the warning screen, and system would boot!
I Had a hunch that might work in this case, and it DID! lol.
Now I'm just trying to put the unbrick.img onto the sdcard I wrote it to... I can't seem to get MTP up, through USB, though ADB works fine...
**EDIT: I forgot, that before I Bricked it, I had the USB settings to DM+MODEM+ADB, cause I WAS unlocking it...
(until a slip of a click and I wrote a backup of the NVdata to the EFS... =/ )
But, after I put the sdcard into my laptop, realized there's not nearly enough room to copy the .img to it...
***SO.... How am I supposed to be able to "dd if=/sdcard/unbrick.img of=/dev/mmcblk0 bs=1024 count=168960"?
I can't put the .img on the sd? Do I put it on the internal? or do I put it on another sdcard and put it in??
**** ACTUALLY, NVM.... THAT'S what I'm gonna do! XD ha
*****
[email protected]:/ # dd if=/storage/extSdCard/unbrick.img of=/dev/mmcblk0 bs=1024
count=168960
ck.img of=/dev/mmcblk0 bs=1024 count=168960 <
168960+0 records in
168960+0 records out
173015040 bytes transferred in 9.488 secs (18235143 bytes/sec)
[email protected]:/ #
=AWESOME!
Click to expand...
Click to collapse
Dangit! STILL can't get it to boot back up without the sdcard in it...? =/
Did you flash the stock firmware in odin...?
Also are you SURE that you have a HARD brick? It sounds like you've got a soft brick which has nothing to do with the method we are using here.
Sent from my SPH-L900 using xda app-developers app
M1k3Carson1369 said:
Dangit! STILL can't get it to boot back up without the sdcard in it...? =/
Click to expand...
Click to collapse
you need to have teh sdcard in there, boot to download mode and flash a full odin tar that includes the bootloaders.
once that's all said and done youll be good
shabbypenguin said:
you need to have teh sdcard in there, boot to download mode and flash a full odin tar that includes the bootloaders.
once that's all said and done youll be good
Click to expand...
Click to collapse
Dang! Samsung-Updates is giving me a hard time trying to download from the links (tera-something 7 something-gator)...
Alright, if that's the only choice... =/ ha
ecs87 said:
Did you flash the stock firmware in odin...?
Also are you SURE that you have a HARD brick? It sounds like you've got a soft brick which has nothing to do with the method we are using here.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Yes, I'm quite sure. Read back through the original thread, you'll see my description of it.
**Oh, you know what? While I wait for a successful download of complete stock rom, I'm gonna plug back into the box, and see if maybe rewriting the original backup of the EFS will fix it... (It was originally a mis-click that bricked it to begin with.. Accidentally wrote a backup of the NVdata to the EFS 0_o)
Worst case scenario; I end up still waiting for the download anyway! (if I can ever get it to start dl'ing)
M1k3Carson1369 said:
Worst case scenario; I end up still waiting for the download anyway! (if I can ever get it to start dl'ing)
Click to expand...
Click to collapse
Do you have the SM-N900T? I can pm you my Dropbox link to download the stock firmware.
Sent from my SM-N900T using Tapatalk 2
lm that guy said:
Do you have the SM-N900T? I can pm you my Dropbox link to download the stock firmware.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
That would be AMAZING! I'd really apreciate it. Thanks!
Hahaha! Success!!!! >=p
WOW!!!
I gotta say, when the only Sign of life I got were "QHUSB_BULK" and Google only found FIVE hits relevant, which were all questions about it as well!?! I was pretty distraught. Thought for sure I'd end up having to send for JTAG, or worse, a replacement... 0_o
But Now, Beyond my most wishful thinking, an unbrick method so simply straightforward and effective.... I'm still trying to pull my Jaw back up...
Thank you all; msmercy42, noobtoob, ecs87, aiti1980, shabbypenguin, lm that guy, & especially zinnium (for testing/confirming)!..! And any contributors whom I failed to mention!
Thanks for all your experience and efforts! That right there is why these forums exist...
Hey I appreciate the thanks, you're welcome!! Just glad to help! This is exactly what I started the thread for! Couldn't have done it without the big time developer support, and from Senior members you listed above - we made a great team!! Merry Christmas!
msmercy42 said:
Hey I appreciate the thanks, you're welcome!! Just glad to help! This is exactly what I started the thread for! Couldn't have done it without the big time developer support, and from Senior members you listed above - we made a great team!! Merry Christmas!
Click to expand...
Click to collapse
@msmercy42, i really did think you had completed it back on the original thread. It was so goofy when it kicked on right before I read you email that you never got it to work. I was like, what?????
That download sucks right now from Samsung updates. With Hotfiles gone, we are all going to have to get use to slow ass downloads. Mine took like 10 hours and I even paid for one of the services.... TOTALLY NOT WORTH IT.
I still don't get how you thought that as I never once posted that I managed to unbrick mine. In fact mine technically is still bricked as I do not have the proper size sd card at the moment.
I never even implied it
---------- Post added at 02:18 AM ---------- Previous post was at 02:10 AM ----------
Also a proper dd command in terminal will write the image to the phone, therefore negating the necessity of Odin. However that is entirely by choice. In my opinion, unless you are very comfortable using powerful Linux commands that could damage your phone, thus rendering it unusable - then Odin is a better choice as it is a powerful software flashing tool that can allow you to control multiple functions in a single operation.
I'll throw a N900T Odin tarball I have stashed away onto my mediafire account. It should deliver decent speeds and it won't get shut down for excessive traffic (COUGHDROPBOXCOUGH). Just gotta drag my ass into work today to do it.
Sent from my SPH-L900 using xda app-developers app
ecs87 said:
I'll throw a N900T Odin tarball I have stashed away onto my mediafire account. It should deliver decent speeds and it won't get shut down for excessive traffic (COUGHDROPBOXCOUGH). Just gotta drag my ass into work today to do it.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
HA! I posted the recovery thread via Heimdall here a while back, right before we met through this thread. Within 10 minutes, I hit my "threshold" with drop box. Moved to mediafire and haven't looked back.
Sent from my SM-N900T using Tapatalk

TF300T Linux Development Thread (For all your Linux concerns)

I figured I would make a Linux Thread for this device that was more broad than the current Xubuntu one that already exists here http://forum.xda-developers.com/showthread.php?t=2190847 . I am going to figure out how to port different distros to this device over the next few months and I am aiming at getting Fedora, Debian, and possibly Arch Linux if I have time. I was disappointed by the lack of Linux development for this tablet so I decided to learn how to port to this tablet myself and take action.
*********CURRENT ROMS AND BUILDS OF LINUX FOR THE TF300T (I am not the developer of any of the builds below.)*********
---TF300T Xubuntu 13.04 : http://forum.xda-developers.com/showthread.php?t=2190847---
---TF300T Arch Linux : http://forum.xda-developers.com/showthread.php?t=1918849---
---TF300T Ubuntu Touch : http://forum.xda-developers.com/showthread.php?t=2165171---
---TF700T Kexecboot Linux (not sure if compatible with TF300T or not.) : http://forum.xda-developers.com/showthread.php?t=2387133---
If anyone would like me to add something to this list shoot me a PM and I will gladly add more. I have a busy life though so I am not going to always be able to add things 24/7.
good idea to start a new thread, maybe either add in the main post or a reply all the latest images that work/rootfs/kexecboot info so that way its up to date on the main page, i might start gathering all that info for addition i n my post/maybe i'll get around to getting one working on my and cronicle my "quest"
Insane PPC said:
good idea to start a new thread, maybe either add in the main post or a reply all the latest images that work/rootfs/kexecboot info so that way its up to date on the main page, i might start gathering all that info for addition i n my post/maybe i'll get around to getting one working on my and cronicle my "quest"
Click to expand...
Click to collapse
I have a general idea of what I have to do but currently my tablet is bricked and I'm working on getting it fixed (long story on why it is bricked). Anyway does anyone have an idea on where I could start with porting. Again I know generally what I have to do but I don't know where I can start learning to do so.
Sent from my LG-E980 using Tapatalk
rjmxtech said:
I have a general idea of what I have to do but currently my tablet is bricked and I'm working on getting it fixed (long story on why it is bricked). Anyway does anyone have an idea on where I could start with porting. Again I know generally what I have to do but I don't know where I can start learning to do so.
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
what kind of brick? mine was down for a long time becuase of a botched wipe and i lost recovery, the only thing i could do was get to fastboot...but any command would lock it up other than "erase" and turned out there was an extra partition/section that needed to be erased before i could flash a stock img/recovery back to it and start from scratch again.
Insane PPC said:
what kind of brick? mine was down for a long time becuase of a botched wipe and i lost recovery, the only thing i could do was get to fastboot...but any command would lock it up other than "erase" and turned out there was an extra partition/section that needed to be erased before i could flash a stock img/recovery back to it and start from scratch again.
Click to expand...
Click to collapse
I tried flashing a recovery from terminal inside of twrp and so the device loops at the ASUS logo and won't go into fastboot or boot into the system or go into recovery. I don't know what to do.
Sent from my LG-E980 using Tapatalk
Insane PPC said:
what kind of brick? mine was down for a long time becuase of a botched wipe and i lost recovery, the only thing i could do was get to fastboot...but any command would lock it up other than "erase" and turned out there was an extra partition/section that needed to be erased before i could flash a stock img/recovery back to it and start from scratch again.
Click to expand...
Click to collapse
I will send you a PM nvm
Sent from my LG-E980 using Tapatalk
Any news?
aurel33 said:
Any news?
Click to expand...
Click to collapse
My tablet is bricked and I cannot fix it so I would say no
Sent from my LG-E980 using Tapatalk
I'm not fixing my tablet guys. I'm probably going to just purchase a MINIX Neo X-8H android set top box instead because it costs almost the same for what I have planned repair wise.
Sent from my LG-E980 using Tapatalk

Categories

Resources