Related
Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are
Great job!
Sent from my Inspire 4g using XDA Premium App
I have added some comments on the talk/discussion page on the wiki. If there is any specific topic you need help on in the wiki let me know.
TheManii said:
Finally went and made the beginnings of a general flashing guide that should eventually cover the basics of everything streak related.
forum.xda-developers.com/wiki/index.php?title=Dell_Streak/Flashing_Guide
For the time being I ask that noone directly adds to the list and instead gives me the details to add myself. As it's a wiki I cannot force anyone to do this but i WILL edit it to match the phrasing or possibly remove it if it's redundant.
It is intentionally not excessively verbose/detailed as too much additional detail is only needed if you're completely new to flashing/messing with software.
It doesnt handhold your way though flashing stuff, if you dont know how to use the command line you should NOT be flashing roms as when you brick you only have your self to blame for not having the needed prereq ability pc wise.
It also only covers windows as I only work/dev on windows, if anyone on *nix/osx wants to give me the OS specific details i'll go ahead and add it
It's also missing most of the details on how to use QDL tool as i've never used it or needed it. I need someone to add/help me add the details in the same guide style without handholding users though using it
It's also very generic as installing most roms dont have specific requirements to them (excluding setting up SD's install.txt which is it's own thing)
it does NOT and will not cover using automated tools such as Gingerbreak or mutlirecovery flasher as automated tools ultimately mean that you do not wish to read the instructions on how to do it properly. (on the streak at least) (no offense to respective makers)
edit: it should also NEVER contain links to the forum and especially "read this post to do xxx" stuff, it should be more or less self contained except with regards to downloading files, which should either be direct links (preferably not on a filesharing site like multishare/etc) or links to another section of the wiki containing links
I know there's a couple users about with compiled guides but I cant recall who/which offhand as I dont need them myself. I'd like your input whoever you are
Click to expand...
Click to collapse
Thanx!
I own HD2 from almost 3 years, i want to try something new with it, so i decided to put Android on the phone. I want to ask here, first, whats the difference between NAND and SD versions, NAND mean its going on the phone memory like the windows? Whats better/faster? Whats easiest to boot/install? I dont want to read all threads all night long, just want some good android rom, or few good android roms to try ... and some advice to be NAND or SD version ... and also, android 2 or 4? i dont know anything about android ... please help. Any advice will be appreciated!
It depends which is easier. I had a problem with partition SD for 4 partitions But with nand there might be problems for novice too. You have to flash HSPL, and then CLK (better than Magldr I think). But then it is easy. SD is on SD, so you have 2 systems at the same time: stock WM6.5 and android which you start by exe in WM. Nand roms fully replaces stock WM. I don't know which is faster, but I prefer NAND. If you are not going to play heavy games, then choose Android 4 with HWA, if just for phone and apps, then 2. And we cannot tell you which rom (system, one of many as you see ) is the best for you - everyone has to try it himself, my experiences might be different than yours If you want to know more, read tutorials or write here - I or someone else will help you.
PS I recommend you tytung's or dorimanx's rom. Or sense rom if you liked it in WM
There's a difference between being new to Android and not being able to read. Use the search tool and every single one of your questions can and have been answered.
Sent from my HTC HD2 using XDA
Nigeldg said:
There's a difference between being new to Android and not being able to read. Use the search tool and every single one of your questions can and have been answered.
ya and what are forums for but to look at,,, people repeating the same old **** constantly. It does not help anyone to look at the words people SAY AND THEN TO ridicule other people constantly . GIVE IT A BREAK. ARE YOU THE ONE THATS FRUSTRATED. GET A GRIP. THIS IS LIFE.
ROCK AND ROLLLLL....................................
Click to expand...
Click to collapse
shanman-2 said:
Nigeldg said:
There's a difference between being new to Android and not being able to read. Use the search tool and every single one of your questions can and have been answered.
ya and what are forums for but to look at,,, people repeating the same old **** constantly. It does not help anyone to look at the words people SAY AND THEN TO ridicule other people constantly . GIVE IT A BREAK. ARE YOU THE ONE THATS FRUSTRATED. GET A GRIP. THIS IS LIFE.
ROCK AND ROLLLLL....................................
Click to expand...
Click to collapse
well if people would follow the FORUM RULES AND SEARCH
and mods would be more worried about the 500 threads about the same thing and delete them instead of deleting 4 or 5 offtopic posts
Click to expand...
Click to collapse
Stop it moderators
come on man, if u find it frustrating to delete 500 posts quit the job man. Atleast dont ridicule the new people.
Anyways, to the person who asked, The NAND version is a bit difficult to install but as it is on internal memory, it is much faster and stable than the SD version. The sd version can be booted up anytime for your stock WinMo 6.5. so u have two Os at any one time. i wud go for NAND but if u are new to this first try SD versions.
adil1508 said:
come on man, if u find it frustrating to delete 500 posts quit the job man. Atleast dont ridicule the new people.
Anyways, to the person who asked, The NAND version is a bit difficult to install but as it is on internal memory, it is much faster and stable than the SD version. The sd version can be booted up anytime for your stock WinMo 6.5. so u have two Os at any one time. i wud go for NAND but if u are new to this first try SD versions.
Click to expand...
Click to collapse
He isn't a mod? Plus you're giving incorrect information. The NAND version is NOT difficult to install, if you just READ. Seriously people, this is exactly what I mean. Reading=good, and the internet contains almost anything you could possibly want to know if you look properly. This guide could not be simpler, even for a newbie like I was. I'm 15, and flashed Android on this phone when I was 14 (plus I don't do any computing or IT in school or anything) so as long as you speak English, you can understand this guide with ease.
shanman-2 said:
ya and what are forums for but to look at,,, people repeating the same old **** constantly. It does not help anyone to look at the words people SAY AND THEN TO ridicule other people constantly . GIVE IT A BREAK. ARE YOU THE ONE THATS FRUSTRATED. GET A GRIP. THIS IS LIFE.
ROCK AND ROLLLLL....................................
Click to expand...
Click to collapse
I couldn't quite understand your first point (three commas doesn't really help me much) as there's a distinction between 'what are forums for but to look at?' and 'what are forums for but to look at people repeating the same old **** constantly'. Both are still wrong, but the first is far more correct. Forums are for sharing information with a wide variety of people. This includes of asking and having your questions answered, but it also includes SEARCHING the forum for your answer. These questions have already been asked and answered a tonne of times. If he searched he could have found the answer. I reckon that theoretically we could fit all of the different non ROM-specific questions which get asked here within just 5 pages at the very most, rather than having the forums span on for ages.
Nigeldg said:
He isn't a mod? Plus you're giving incorrect information. The NAND version is NOT difficult to install, if you just READ. Seriously people, this is exactly what I mean. Reading=good, and the internet contains almost anything you could possibly want to know if you look properly. This guide could not be simpler, even for a newbie like I was. I'm 15, and flashed Android on this phone when I was 14 (plus I don't do any computing or IT in school or anything) so as long as you speak English, you can understand this guide with ease.
I couldn't quite understand your first point (three commas doesn't really help me much) as there's a distinction between 'what are forums for but to look at?' and 'what are forums for but to look at people repeating the same old **** constantly'. Both are still wrong, but the first is far more correct. Forums are for sharing information with a wide variety of people. This includes of asking and having your questions answered, but it also includes SEARCHING the forum for your answer. These questions have already been asked and answered a tonne of times. If he searched he could have found the answer. I reckon that theoretically we could fit all of the different non ROM-specific questions which get asked here within just 5 pages at the very most, rather than having the forums span on for ages.
Click to expand...
Click to collapse
chuckles it wouldnt be pretty if i was a mod lol
HTC + Android = PERFECT MATCH!!
Try starting by READING the guide, it's not that hard to do. Just follow the instruction and READ carefully. Dont skip the sentence if u don't want to Brick your phone.
+1 Vote for NAND Android
Anyway i can't tell what's perfectly right for you. U will have to try it your self.
I tried like 4-5 ROM until i found what's right for me. However if u can do it once, the rest is just a piece of cake.
Like the other guyz said. Nearly all problem that u have, someone had already post the solution for that keep searching if u encounter any trouble.
While you were arguing about my question, and writing long posts, instead of giving your advice ... i installed one NAND rom, Energy one, but i think it installed on the SD ... because it asked me to format 1024mb on the SD card, so it is not really a NAND one i think ... and also, it looks a little bit slow ... freezes from time to time, not so smooth as expected ... and i read many articles, but i just wanted an advice, why to try all roms, when you can tell me 1 - 2- 3 roms that worth the try? This forum is so full with information, that for new people like me its too difficult to see the important threads for our needs, thats why we ask you, the people being long time here, tried more of the roms, and read lall the things, because i dont want to loose mu life in reading here, for thing i can do for 10 min, and then never look back for it ... SO Finally, few people helped me, the rest was arguing ... and who is the smartest of all of you? Instead of writing long posts telling me to read, you can simply write 3 sentences ... I am using this rom, i tried this and this and are also good, NAND means on memory like windows, SD means on card, NAND is faster, read "This" thread it will help you with your problem ... its so simple to help people, do you think i need to read all this forum, to install and use android? and this is forum with live people, not internet book ... so asking is part of forum, so, i am new to android, not to forums and reading ... thats why ... stop telling people to stop asking, be nice, if you dont want to answer, then dont ... if you feel like you want to help, do it ... and you will save you alot of antystress pills! Peace
sadmind said:
While you were arguing about my question, and writing long posts, instead of giving your advice ... i installed one NAND rom, Energy one, but i think it installed on the SD ... because it asked me to format 1024mb on the SD card, so it is not really a NAND one i think ... and also, it looks a little bit slow ... freezes from time to time, not so smooth as expected ... and i read many articles, but i just wanted an advice, why to try all roms, when you can tell me 1 - 2- 3 roms that worth the try? This forum is so full with information, that for new people like me its too difficult to see the important threads for our needs, thats why we ask you, the people being long time here, tried more of the roms, and read lall the things, because i dont want to loose mu life in reading here, for thing i can do for 10 min, and then never look back for it ... SO Finally, few people helped me, the rest was arguing ... and who is the smartest of all of you? Instead of writing long posts telling me to read, you can simply write 3 sentences ... I am using this rom, i tried this and this and are also good, NAND means on memory like windows, SD means on card, NAND is faster, read "This" thread it will help you with your problem ... its so simple to help people, do you think i need to read all this forum, to install and use android? and this is forum with live people, not internet book ... so asking is part of forum, so, i am new to android, not to forums and reading ... thats why ... stop telling people to stop asking, be nice, if you dont want to answer, then dont ... if you feel like you want to help, do it ... and you will save you alot of antystress pills! Peace
Click to expand...
Click to collapse
And if you found all of that information on your own, why did you have to bother creating this thread? Also, you just don't want to read do you? When you said 'format 1024mb on my SD card' you mean creating an SD-EXT partition. Again, if you had read carefully you would realise that this is necessary for Sense 3.5 builds on EU HD2s and you would know that that is a NAND ROM. I was confused about this at first as well, so what did I do? I did some READING and figured it out logically. Finally, if you're experiencing lag and stuff, try a lighter ROM such as a CM7/MIUI/CM9/AOKP ROM, Sense is very bloated and (IMO) too slow compared to CM9. Plus, CM9 has full HWA.
I can recommend NAND:
-Dorimanx 3.1.7 CM7 rom (install 3.1.7 and not 3.1.7.1 - broken script)
-Tytung's roms (there are some)
-TouchWiz roms (stable for me)
-And HWA roms, read about them, I use Nightlies and all right
And most roms, like Sense roms (including Energy) needs EXT partitions for additional data.
And better use cLK bootloader.
Thing is, posts with questions that don't have or hard to answer (can't be searched about) don't get any replies. :screwy:
hengsheng120 said:
Thing is, posts with questions that don't have or hard to answer (can't be searched about) don't get any replies. :screwy:
Click to expand...
Click to collapse
Yep, that's basically one of the main reasons I dislike it when people post unnecessary threads. Not only does it clutter up the forum but it also shoves other people with genuine problems off the first page, and their questions are unanswered. This most certainly isn't fair in my opinion.
Here you go...
sadmind said:
While you were arguing about my question, and writing long posts, instead of giving your advice ... if you feel like you want to help, do it ... and you will save you alot of antystress pills! Peace
Click to expand...
Click to collapse
I posted this a while back and was written like it was going to be your very first attempt at putting android on your phone. You can still follow this guide from step one till the end to make sure your doing everything correctly... Hope this helps and if it does hit up that thanks button at sometime.
(Im attaching most of the files you need at the end of the post. You'll have to find the radio, step 2, yourself because i cant compress it enough to fit under the 8mb attachment limit on xda. This is just in case you dont have them already or your not using the HD2 Toolkit)
THESE STEPS ARE TO BE DONE AFTER THE OP INITIAL PREREQUISITES i.e. windows mobile device center, activesync, proper spl version...
FOR NAND
--------the following steps (1 - 3) are to be preformed while at the tri-color boot screen (easiest way to reach is to turn off your phone while its connected to your PC then immediately hold volume down button till you see it n wait for it to say usb in the white section).
(by the way your device will ALWAYS automatically restart itself after a couple seconds if it is shut down while plugged in via USB to either a wall/car charger or hooked up to a PC this is normal)
1. install hspl3/hspl4
-run the "HSPL3_PKG/HSPL4_PKG" file. should be the only one in there
-make sure you select 2.08.HSPL in the setup and go thru the wizard just like you would any other. It will only take a few moments to execute and once it finishes it will auto reboot your device. MAKE SURE AS SOON AS YOUR DEVICE TURNS OFF YOU HOLD DOWN ON THE VOLUME KEY IMMEDIATELY TO GET BACK TO THE TRI COLOR BOOT SCREEN.
2. install radio
-run the "customRUU" file with the HD2 icon in the radio of your choosing
-it will operate in a similar fashion as the HSPL3/4, automatically turning off device upon completion... make sure you hold down on the vol key again to get yourself back to the tri color boot screen.
3. install magldr113
-make sure your selecting "rom update utility" in the magldr113 file. dont run the "DAF" it wont work properly if you do and youll get errors
-BUT THIS TIME AS IT TURNS ITSELF OFF HOLD DOWN THE POWER BUTTON ON YOUR DEVICE AS IT BOOTS UP UNTIL U GET TO MAGLDR AND CONTINUE TO HOLD IT DOWN UNTIL YOU SEE ABOUT 12 DIFFERENT OPTIONS...
[B4. install CWM recovery [/B]
-go to option 5 "USB Flasher" and hit the green call key. wait a few moments till it shows USB....USB make sure the second usb pops up and your PC recognizes the connection. then when it does sync you get to......
-while still in the usb flasher mode above, simply run you desired CWM recovery which should the one your developer recommends for the builds as the requirements tend to vary from rom to rom.
-this is achieved by selecting the "DAF" file from the clockworkmod recovery your using
-and again this installer will shut off your device upon completion and HOLD DOWN THE POWER KEY LIKE ABOVE TILL YOUR BACK AT THE MAGLDR MAIN MENU (with options 1-12).
5. install rom
-go to option 8 "AD Recovery" and hit the green call button to enter into the CWM recovery u just installed
-after it loads up (GO!GO!GO!) go down to the "mounts and storage" option that is third from the bottom and hit the call key.
-once there go to the last option "mount USB storage" and hit the call key.
-give your PC a few moments to recognize the sd card for your device and choose to open it when your PC prompts with the regular file explorer or just find it and double click on the newly recognized drive (sdcard) if your PC doesnt auto prompt you.
-the new drive (sdcard) should be empty (depending...) then just find the desired rom you chose to use, right click on it and copy.....then over to the new drive (sdcard) and paste. might take a min or two depending on the roms size
-once the copying is complete hit the call button to "unmount" your sdcard then the back button on your device till your back at the CWM main screen
-go to the fifth option down and "install zip from sdcard" and hit the call button
-select the second option "choose zip from sdcard" and select the zip file you just copied to your sdcard. then it will begin to install the rom and all rom install times vary by build. some take a minute, some seem like they take forever.
-once installation is complete hit the back button till your back at CWM main screen and choose the last option which is to "power off"
-then tap the power button(if u unplugged it from usb otherwise it wil reboot by itself) to turn on your device and give it some time for the initial boot and load as it has to set up everything u just installed. subsequent boot wont take as long but again it can all vary from rom to rom.
-after initial load and a successful bootup you should arrive at ether the lockscreen or a startup screen. give the rom a few more mins to settle and dont hit any buttons. then unlock the device or skip through the startup options and get to the home screen. maybe give it another min to settle the launcher and the last bit of data and resist the urge to mess with the features. your gonna hate this but hold down the power button and select power off device from the popup men. i know it sucks but it is best practice when flashing roms and the like. after device shuts off wait a few seconds and turn it back on and let it reboot. should be faster this time and when u get to your lockscreen simply give it a few seconds to settle again, unlock and go to main launcher a wait a couple more seconds for it to finish settling and.....have fun!
Maybe its not so abridged but oh well tried my best to be as clear as possible so people can utilize their HD2 to its fullest potential.
HOPE THIS HELPS and lemme know if i need to edit any information.
Oh yeah and as for ROM selections give these a try:
CM7/gingerbread - Typhoon by Tyween, Dorimanx High End Rom by Dorimanx
Sense 3.x/gingerbread - Team blue Droid by Dansta, Sensation XL stock by carl 1961
CM9/ics - Unofficial AOKP for HD2 by Xylograph, Nexus HD2 ICS by Tytung
There are lots more to choose from, these are just some of the more notable ones that ive used.
DON'T post guides that are incorrect. @OP if you want a proper guide, followthis one. It's actually correct unlike the one posted above.
Check yourself little one
Nigeldg said:
DON'T post guides that are incorrect. @OP if you want a proper guide, followthis one. It's actually correct unlike the one posted above.
Click to expand...
Click to collapse
Well, I did ask (nicely) for corrections. So what part of this is wrong? I use this same procedure for every rom i flash, well plus/minus a few steps. Pretty sure this works as this has helped other people in the past. While Mskip's guide is very useful, to a beginner it can seem lil overwheling with all of the information he provides. Mine was supposed to be a quick run-thru of the steps.
So please inform me, with all that 15 yr old experience, what is not correct...
BLAYZERUNNER said:
Well, I did ask (nicely) for corrections. So what part of this is wrong? I use this same procedure for every rom i flash, well plus/minus a few steps. Pretty sure this works as this has helped other people in the past. While Mskip's guide is very useful, to a beginner it can seem lil overwheling with all of the information he provides. Mine was supposed to be a quick run-thru of the steps.
So please inform me, with all that 15 yr old experience, what is not correct...
Click to expand...
Click to collapse
Sorry about that, didn't see that part. However, there's no need to be patronising, I know a fair amount, and judging by this guide you don't.
BLAYZERUNNER said:
1. run task 29
Click to expand...
Click to collapse
Not correct, HSPL is needed first. You only mentioned 'the OP prerequisites e.g. correct SPL version'. SPL isn't the same as HSPL, and the OP often doesn't contain info like this. Devs don't write guides on how to flash in all their ROMs, plus if this is a newbie guide you should mention this as step 1.
As well as this, Task29 is 100% useless in this case. When you unnecessarily suggest Task29s, people get into the habit of doing them every time they flash. This repeated writing of the NAND can eventually lead to bad blocks.
BLAYZERUNNER said:
3. install hspl3/hspl4
Click to expand...
Click to collapse
I don't think I need to point out your mistake here, you should easily be able to figure it out.
BLAYZERUNNER said:
5. install CWM recovery
-go to option 5 "USB Flasher" and hit the green call key. wait a few moments till it shows USB....USB make sure the second usb pops up and your PC recognizes the connection. then when it does sync you get to......
-while still in the usb flasher mode above, simply run you desired CWM recovery which should the one your developer recommends for the builds as the requirements tend to vary from rom to rom.
Click to expand...
Click to collapse
I would like to stress that you call this a guide for newbies. This isn't clear enough. It implies CWM version (no actual mention of partition sizes, which is key)
BLAYZERUNNER said:
6. install rom
-go to option 8 "AD Recovery" and hit the green call button to enter into the CWM recovery u just installed
-after it loads up (GO!GO!GO!) go down to the "mounts and storage" option that is third from the bottom and hit the call key.
-once there go to the last option "mount USB storage" and hit the call key.
-give your PC a few moments to recognize the sd card for your device and choose to open it when your PC prompts with the regular file explorer or just find it and double click on the newly recognized drive (sdcard) if your PC doesnt auto prompt you.
-the new drive (sdcard) should be empty (depending...) then just find the desired rom you chose to use, right click on it and copy.....then over to the new drive (sdcard) and paste. might take a min or two depending on the roms size
-once the copying is complete hit the call button to "unmount" your sdcard then the back button on your device till your back at the CWM main screen
Click to expand...
Click to collapse
There have been many reports of file corruption when using this method to copy over a ROM. Also, why should the new drive be empty? This would imply you would have to delete the contents of your SD card in order to flash a ROM, which you don't.
Also, no mention of partitioning the SD card. You've listed Sense 3.x ROMs as recommended, yet you need an SD card partition to run these. A newbie would not know this of course and would probably end up creating a new thread about 'why isn't my ROM working?? '.
This guide, whilst you're obviously trying to do a good thing by helping people, would just confuse a newbie, not help them. By following it to the letter you'd probably incorrectly/unsuccessfully flash Android.
- I'm using IceCreamTosti v1.1a [AOKP B36][HWA][4.0.4][marc1706s_ics_0.1.1] by Xylograph.
anyway. all the great rom is the most viewed one i think.
but to define which ROM is the BEST is very difficult because TASTE is different hehehe.
Awww snap!, where do i start...
Nigeldg said:
Sorry about that, didn't see that part. However, there's no need to be patronising, I know a fair amount, and judging by this guide you don't.
Not correct, HSPL is needed first. You only mentioned 'the OP prerequisites e.g. correct SPL version'. SPL isn't the same as HSPL, and the OP often doesn't contain info like this. Devs don't write guides on how to flash in all their ROMs, plus if this is a newbie guide you should mention this as step 1.
As well as this, Task29 is 100% useless in this case. When you unnecessarily suggest Task29s, people get into the habit of doing them every time they flash. This repeated writing of the NAND can eventually lead to bad blocks.
I don't think I need to point out your mistake here, you should easily be able to figure it out.
I would like to stress that you call this a guide for newbies. This isn't clear enough. It implies CWM version (no actual mention of partition sizes, which is key)
There have been many reports of file corruption when using this method to copy over a ROM. Also, why should the new drive be empty? This would imply you would have to delete the contents of your SD card in order to flash a ROM, which you don't.
Also, no mention of partitioning the SD card. You've listed Sense 3.x ROMs as recommended, yet you need an SD card partition to run these. A newbie would not know this of course and would probably end up creating a new thread about 'why isn't my ROM working?? '.
This guide, whilst you're obviously trying to do a good thing by helping people, would just confuse a newbie, not help them. By following it to the letter you'd probably incorrectly/unsuccessfully flash Android.
Click to expand...
Click to collapse
First off, I did say that i posted this elsewhere, soooo the OP that was referenced wasnt this threads OP or a devs OP, it posted in a different thread where the OP had a huge long guide that again had a lot of information to sort thru and mine was an attempt to streamline that process.
The spl version i spoke of was in reference to...
IMPORTANT: To install/uninstall this HSPL3 there must be any SPL version from this list on your device:
SPL 1.42.0000, SPL 1.62.0000, SPL 1.66.0000, SPL 2.07.0000, SPL 2.08.0000, SPL 2.10.0000, SPL 3.03.000 - courtesy of mskips guide
I thought a task29 would be good in this case because this OP in this thread said he had tried an sd card version or something or whatever he had done and it wasnt working very well so why not get everything off there he may have done. Also your task 29 causing bad blocks might be true, but its no different from flashing roms that write to nand or installing a bunch of apps n such. If i am not mistaken they all write to nand anyway as well, so by your logic you better be careful installing roms... might lead to bad blocks! OH NO!
If this is one of the first times you flash android to nand you probably dont have much or anything at all on your sdcard. Like i said I POSTED THIS ELSEWHERE for a quick step by step for a beginners. Ive been installing roms this way for a couple years on this device and have never had any problems with file corruption... only spoiled know it all little kids.
The CWM file i included has a 180 system layout which will work with most CM7 & CM9. I figured if it came to it and he need another version he could just edit the cfg file or find the correct one as a good number of devs will just include this in their OPs.
And yes step 3 is a little redundant because you have already (obviously) had to do this. I included it because i found that some people were just choosing the first option to install 2.08 and not 2.08hspl in the HSPL3/4 wizard. The redundancy was to make sure people are clicking the right option. I even did this once a year or so back and didnt catch my mistake right away.
And as for partitioning the sdcard for sense 3.x roms I was pretty sure that Dansta34 and Carl 1961 roms dont require this anymore as they trimmed down the roms and im pretty sure it isnt required for tmoUSA devices because of the increase in internal memory while the EU version did or does because it has half the space. Not sure on this because the last time i was running a sense3.x rom was last fall so there is a chance i was mistaken. Plus if you do need to create a ext3/4 partition im pretty sure its stated in the roms OP.
Next time you flash a rom go ahead and follow the above steps and i bet you it works.
And you started the patronizing by the way you have chosen to respond to sadmind's posts... thats that whole pot calling the kettle black thing...
So quit trolling threads and further clogging them up with your know it all nonsense... a sign of your immaturity. Instead of helping the guy with a post or two YOU clog threads up by being unhelpful and repeating the "its posted elsewhere so look for it" line. Its a quick way to get over a thousand posts thats for sure! And why waste your time posting in this thread anyway if you not gonna help. Just ignore the question and move on already. Damn kids!
Hey guys!
I have spent the past 2 days getting this one error and after hours of reading up and trying to get all the facts straight, I just can't figure this one out!
I have cyanogen mod 10
I have Skrillax unlocked bootloader v8
and then I have all the files necessary for Ubuntu and Bodhi. Plus recoveries.
Mostly, I have been trying to follow
HTML:
http://forum.xda-developers.com/showpost.php?p=22201465&postcount=351
single post, which works great up until the point of booting! I seem to get an error that says:
"busybox: 'busybox' is not an absolute path Could not find /dev/mmcblk0p7! Dropping to a shell.
sh can't access tty; job control turned off"
(there's more after that but it doesn't seem to pertain to anything of importance that I can tell)
I just can't get over that error! I read about, but it seems like there is some dialog between other users that happened, and the conversation got changed way too fast that I couldn't understand what was going on!
If I am in the wrong area just let me know and I can move, or repost my question on a different thread. I just can't seem to find the direct answer through google, forum search, or even *shiver* Bing.
Thanks for the views, thanks for the help (if you can!).
:angel:
The odd one out!
Looks like you are one of the unlucky owners of A500 with a different file system than most A500. You will probably only be able to use the external card method for now. If some one compiles a new Kernel (recovery) then you will be able to use internel card method. Check the Dual Boot thread in the General section I made a more detailed explanation. Hope that helps
Thanks!
themechaniac said:
Looks like you are one of the unlucky owners of A500 with a different file system than most A500.
Click to expand...
Click to collapse
Thanks for the reply! I guess that answers all of my questions! Hopefully I can get something setup .
calebcoverdale said:
Thanks for the reply! I guess that answers all of my questions! Hopefully I can get something setup .
Click to expand...
Click to collapse
Ill try to compile a new recovery.img to point to 08 but no promises :-\
Consider this thread your one place to chat or anything else related to jellybean on the Asus Transformer.
I need everyones help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
All other threads on this topic will be closed.
Keep all your posts in this thread polite and make sure you follow the rules
For all your JB needs go [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]
and
[INDEX][08 OCT 12] INDEX of ROMS/RECOVERY/ROOT/GUIDES/FIRMWARE/KERNEL/VIDEOS/etc..
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
2. Member conduct.
2.1 Language: XDA is a worldwide community. As a result what is ‘ok’ to say in your part of the world may not be ok in someone else’s part of the world. Please think about who is reading what you write. Keep in mind that what you think of as acceptable use of language may not be acceptable to others. Conversely, while reading member posts, remember that word you find offensive may not be to the writer. Tolerance is a two way street.
2.2 Nudity: XDA is used by people of all ages, including minors. It's not acceptable to post nude/pornographic imagery, which includes exposure of the male or female genitalia or of female breasts.
2.3 Flaming: XDA was founded as a group of people sharing information about certain mobile phones. Sharing does not involve virtual yelling (flaming) it does involve working together to solve problems in an environment of mutual respect and understanding. Losing your temper and flaming another member, or group of members, is not acceptable behavior.
2.4 Personal attacks, racial, political and/or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive, therefore none of these types of discussions are permitted on XDA.
2.5 Courtesy towards other Members: Treat new members the way you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instruction when you can and always with respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.6 All members are expected to read and adhere to the XDA rules.
3. Post only using a clear subject and message.
You're most likely to receive a helpful answer to your question if you use a short subject title that describes your problem and a message that explains in detail what your problem is and what you've tried to solve it.
4. Use the English language.
We understand that with all the different nationalities not everyone speaks English well, but please try. If you're really unable to post in English use an online translator, You're free to include your original message in your own language below the English translation.
5. Post a message only once.
As a large forum we don't need unnecessary clutter, You're free to edit your message as you like, so if you do not receive an answer revisit your message and see if you can describe your problem better. Not everyone is online at the same time, it might take a while before you receive an answer.
6. Do not post warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community
7. Do not spam.
If you wish to advertise a product, contact us we provide ads. But do not post it in the forums, it will be removed and you're likely to receive a ban.
You are however allowed to sell used goods like your own device, parts of your device or accessories for your device in the marketplace forum, please read the rules there before posting. (This rule includes signatures, if you use a signature it will appear in your post)
8. Donations.
We appreciate all donations to xda-developers.com, it keeps our forum online and well maintained. As a user you're allowed to ask for donations in your signature as a thank you for your hard work. However donations up front are not allowed, this forum is about sharing, not about getting paid to do something, that's what your job is for.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
10. Help others if you can.
If you see posts from others where you can help out, please do. This place exists because people are helping each other, and even if you are relatively new to the matter, there's probably already quite a few people newer than you that would benefit from what you've learned. Don't be shy.
11. Don’t post with the intention of selling something.
Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and offer support, but not to post with the intention of selling. This includes promoting sites similar/substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software, or commercial services. unless you’re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if the following conditions are met:
A) the site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership who actively maintains XDA-Developers' support thread(s) / posts, related to the download,
B) the site is a relatively small personal website without commercial advertising/links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.
Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by the dev or freely share it. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie allowing certain people to use it and not others). Should the dev decide to start sharing the work with others, the work automatically becomes fair game for all to use.
In regards to permissions, same rules remain for this but if permission was already given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under severe circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay per click links and other income generating methods are forbidden. Do not use xda-developers as a means to make money.
14. Create only one User Account
You are allowed one User Account at xda-developers. If you create additional accounts, Moderators will disable them and your original account may also be disabled or infracted.
15. Keep posts/threads on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is your posts / threads must be relevant to the Forum / thread in which you are posting.
16. Bumping Threads (posting simply to force a thread to the top of the thread queue)
Do not "bump" a thread more than once per 24 hours.
Click to expand...
Click to collapse
Thanks,
It's good to remember that we have rules in xda.
If you are a new member, junior member or young senior member, force yourself to read these rules.
This is to avoid to close your OP or delete your post.
And then especially seek and read a bit more before posting anywhere.
TF300T users are welcome
and enjoy some good time on this thread and share your passion for your device
Hi guys I have a tf300T
I must say my tf300 was updated 7 days ago to JB from OTA asus update, so I don't need if there is something locked features I need to un lock...any help would be very appreciated...
I followed all the steps, but when I launch the "fastboot" I got this message
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\mezzalana>cd documenti
C:\Documents and Settings\mezzalana\Documenti>cd downloads
C:\Documents and Settings\mezzalana\Documenti\Downloads>cd tablet
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>adb reboot bootlo
ader
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>fast boot -i 0x0b0
5 flash recovery tf300t-jb.blob
sending 'recovery' (6524 KB)...
OKAY [ 2.625s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 5.891s
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>adb reboot bootlo
ader
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>adb reboot bootlo
ader
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>
Click to expand...
Click to collapse
then if I try to select the rck icon and flash the superuser zip file I got a dead android with a red exclamation mark on his stomach...
any help?
I solved, we need to download an pak directly from asus it is called "boorloader unlock" in this way you unlock the device and you can Apply all the steps. I think is better to say this, some noob like me could be very confused.
the asus link is
http://www.asus.it/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
In the guide there is the name of the apk bloatware files...but how can I delete them? Root explorer?
marcomesa said:
I solved, we need to download an pak directly from asus it is called "boorloader unlock" in this way you unlock the device and you can Apply all the steps. I think is better to say this, some noob like me could be very confused.
In the guide there is the name of the apk bloatware files...but how can I delete them? Root explorer?
Click to expand...
Click to collapse
Ah ah ah, you are really a joker.
Do you think that I give the pain to write and update an index for TF300TF / TG for nobody reads it.
and in this index, you will find the unlock tool and the download link
You will find the link to this index in a large number of posts and the OP.
Therefore take care, and give you the time to read and to search for a little!!!!
Ok thanks for the teaching...you need patience with people like me, I'm still learning
marcomesa said:
Ok thanks for the teaching...you need patience with people like me, I'm still learning
Click to expand...
Click to collapse
And for your information, you will find a "THANKS" button just left down.
It will be cool to write thanks, but it will be better to click "THANKS"
Since my thread got closed, even though it was about the "general procedure" and not specifically discussing Jelly Bean in any way, just asking if I might as well use the WW version of a JB-based ASUS official FW instead of the recommended US one, siberian tiger requested me to post this here.
Hey there! I'm getting a TF300 pretty soon and just wanted to make sure I got the necessary steps for some fun with it right..
1st: Rooting
2nd: Bootloader Unlocking
3rd: Upgrading to JB without losing root
This correct so far? Is the US Update mentioned in the 3rd step really necessary or can I use an equivalent WW version of the Update?
Please don't hit me with the stick, I'm just trying to get the most out of the TF300 without turning it into a doorstop.
twiitar said:
Since my thread got closed, even though it was about the "general procedure" and not specifically discussing Jelly Bean in any way, just asking if I might as well use the WW version of a JB-based ASUS official FW instead of the recommended US one, siberian tiger requested me to post this here.
Hey there! I'm getting a TF300 pretty soon and just wanted to make sure I got the necessary steps for some fun with it right..
1st: Rooting
2nd: Bootloader Unlocking
3rd: Upgrading to JB without losing root
This correct so far? Is the US Update mentioned in the 3rd step really necessary or can I use an equivalent WW version of the Update?
Please don't hit me with the stick, I'm just trying to get the most out of the TF300 without turning it into a doorstop.
Click to expand...
Click to collapse
Your thread has been closed in order to regroup all the discussions on JB in general and especially to avoid having too many posts unnecessary and repetitive.
Don't take it as a punishment or anything else. It's not.
It is more convenient to manage the answers.
And for all of your questions, I can say that it's correct
You can buy your TF300T quietly
Does your microsd slot work after update to JB?
gabor94 said:
Does your microsd slot work after update to JB?
Click to expand...
Click to collapse
Yes without problem.
I have a 32 Gb sd card class 10 - it's partitioned: 20 Gb NTFS format (for the movies) - and the rest to Fat32
be care !!!!!! i bricked my tf300t
Hi All..
My TF300t is unlocked and rooted . I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing.
i install universal naked driver
and could enter in APX mode and my pc show apx driver
how can i restore my bootloader and fastboot
i did not have nvflash backup
many thanks
---------- Post added at 03:31 PM ---------- Previous post was at 03:17 PM ----------
Hi All..
My TF300t is unlocked and rooted . I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing.
i install universal naked driver
and could enter in APX mode and my pc show apx driver
how can i restore my bootloader and fastboot
i did not have NVFLASH backup
many thanks
arch.fadi said:
Hi All..
i install universal naked driver
and could enter in APX mode and my pc show apx driver
how can i restore my bootloader and fastboot
i did not have NVFLASH backup
Click to expand...
Click to collapse
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse
It's writing in the OP of the Universal naked drivers. Have you uninstalled your old packages ?
So actually, it's better to uninstall all your packages from your computer, reboot, and re-install U.N.Drivers
And never forgotten to making always backup. It's better to do more than none
Try this and report a feedback
philos64 said:
It's writing in the OP of the Universal naked drivers. Have you uninstalled your old packages ?
So actually, it's better to uninstall all your packages from your computer, reboot, and re-install U.N.Drivers
And never forgotten to making always backup. It's better to do more than none
Try this and report a feedback
Click to expand...
Click to collapse
sorry. but what you mean whit old packages ?
i installed APX driver successfully ,and my pc recognized the tablet as APX device
but the question : any hope to restore bootloader or fastboot in APX mode
thenks
I think that it will be good to read this, if it help you:
Tegra3 Guide: nvflash
Have you made this ?
To do this please reboot your tablet into APX mode by holding down the volume up key during the reboot process. If successful the screen should remain blank and be detected over USB by your computer as an NVIDIA APX mode device.
Click to expand...
Click to collapse
if it's run, you can make this:
To “bootstrap” into nvflash using wheelie simply run the following command:-
Code:
$ wheelie --blob blob.bin
If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
Click to expand...
Click to collapse
or
Have you got those symptoms on your TF ?
- Blank screen,
- apx only detected,
- holding power down does nothing
and if you have those symptoms, the only solution seems RMA, if you don't have a working bootloader and didn't made the nvflash setting process you're done, or backup.
philos64,
Does the stock JB 4.1.1 kernel support NTFS mounting with R/W? How about exFAT?
CrimsonKnight13 said:
philos64,
Does the stock JB 4.1.1 kernel support NTFS mounting with R/W? How about exFAT?
Click to expand...
Click to collapse
I have a 32 Gb sd card class 10 - it's partitioned: 20 Gb NTFS format (for the movies) - and the rest to Fat32
I don't know if it works in Stock, but I'm use it on CleanRom and on JB Overclock without problem.
You can try and make a report after.
Thanks
philos64 said:
I have a 32 Gb sd card class 10 - it's partitioned: 20 Gb NTFS format (for the movies) - and the rest to Fat32
I don't know if it works in Stock, but I'm use it on CleanRom and on JB Overclock without problem.
You can try and make a report after.
Thanks
Click to expand...
Click to collapse
I'll be sure to do that & let you know. I'll be getting a brand new 64GB UHS-1 MicroSDXC card by Thursday, so I'll test it out then.
CrimsonKnight13 said:
I'll be sure to do that & let you know. I'll be getting a brand new 64GB UHS-1 MicroSDXC card by Thursday, so I'll test it out then.
Click to expand...
Click to collapse
I use the NTFS format for the movies, cause I have some movies (for my child) in MKV format (1GB ~3GB)
philos64 said:
I use the NTFS format for the movies, cause I have some movies (for my child) in MKV format (1GB ~3GB)
Click to expand...
Click to collapse
FAT32 supports up to 4GB file size. Anything beyond 4GB would need NTFS or exFAT.
https://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits
You probably don't need NTFS at all unless you are gaining the added benefits of it within JB.
hi I was trying to unlock my g900w8 galaxy s5, I guess I ended up erasing my efs.
I ended up with imei=unknown, the baseband and everything else reads correct. but I keep getting the 'mobile network not available' or the "not registered to network" error'
and no my imei is not blacklisted I just need to get it back on my phone.
I did make a back up of the nv with nv writer and a back up of qcn with qpst. but I did not make a copy of my efs folder.
my problem is I cannot restore my nv nor can I restore my qcn. its getting blocked from some kind of permission. for example when I try to restore in nv writer I get these errors:
Writing NV-items from a file:
Unsuccessfully written NV-items:
00001 (0x0001) - Read only item
00002 (0x0002) - Read only item
00003 (0x0003) - Read only item
00550 (0x0226) - Access denied
00855 (0x0357) - SPC (6 digits) is required
01943 (0x0797) - Read only item
05597 (0x15DD) - Read only item
05598 (0x15DE) - Read only item
10155 (0x27AB) - Access denied
Done.
and similar issues with qcn back up.
is this because of the s5 firmware?
how do I force a successful write?
or if possible how can I extract my efs info from my two back ups?
when I open the qcn file as an archive with 7.zip I do see several folders like EFS_Backup, NV_Items, NV_NUMBERED_ITEMS, Provisioning_Item_Files. but I don't know what to do with them or how to convert them into something I can put back in my phone.
thanks any help would be appreciated.
We're sorry to hear that your phone got messed up. Just goes to show that the very first thing anyone ought to be doing is making backups just in case you need them. That should be common sense but we're all guilty of taking risks sometimes.
However, we can tell that you didn't do much of a search or read more than about two posts in the forum before posting. If you had you would have found countless posts asking this question and the inevitable response i.e. discussing how to change /repair /modify, etc IMEI numbers is not permitted on this forum. It's too easy to abuse or facilitate the trade in stolen phones.
And no, I doubt that the staff will make an exception just for you. You'll have to rely upon Google or possibly your carrier will replace your phone under warranty regardless of cause. Often if you don't volunteer information, they don't really look too closely at why a phone fails. Samsung will have no problem ultimately repairing the original phone when it goes their refurbishment process.
.
fffft said:
We're sorry to hear that your phone got messed up. Just goes to show that the very first thing anyone ought to be doing is making backups just in case you need them. That should be common sense but we're all guilty of taking risks sometimes.
However, we can tell that you didn't do much of a search or read more than about two posts in the forum before posting. If you had you would have found countless posts asking this question and the inevitable response i.e. discussing how to change /repair /modify, etc IMEI numbers is not permitted on this forum. It's too easy to abuse or facilitate the trade in stolen phones.
And no, I doubt that the staff will make an exception just for you. You'll have to rely upon Google or possibly your carrier will replace your phone under warranty regardless of cause. Often if you don't volunteer information, they don't really look too closely at why a phone fails. Samsung will have no problem ultimately repairing the original phone when it goes their refurbishment process.
.
Click to expand...
Click to collapse
thank you for you reply, I have searched, I've searched all over the net even, I do know that talking about changing the imei is not permitted on this forum but in my searches I have come upon many threads regarding imei problems and recovery, coming from this board as well. I have tried many different things and programs, wiped my phone a few times reinstalling the firmware, rooting, unrooting etc. but I still do not have a solution to my problems
I am not trying to change my imei, I lost it while trying to unlock my phone. I am just trying to recover my imei through my back ups or any means to get my phone back up and running.... even if it was just help to get my back ups to actually back up to my phone I would be really greatfull because at the moment it is just a really expensive paperweight.
thank you.
sakohunter said:
I am not trying to change my imei
Click to expand...
Click to collapse
You are trying to change your IMEI. From it's current value to the original one. And posting how to change an IMEI can be expected to be abused by thieves and the like. You can't say, I know the rules say don't explain how to pick locks. but it's okay because i will only use it to get into my own house. Umm, no. Once posted, miscreants will have access to the information as well. No doubt the reason why XDA staff don't allow the type of discussion you want to engage in.
Since you know that this isn't permitted you should have simply dropped it rather than try to justify an exception. If you felt strongly about the subject you could try to persuade staff to change the rules, rather than skirt them. The latter suggests that you are ignoring them mostly because it would be an expedient way to fix your phone.
.
ok, im not here to argue with you, I was only seeking help and being honest about it.
I could have left imei out of my whole post and just asked for help in restoring my nv and qcn backups.
or rather why my phone is not writing the backups. which is my whole intention.
ive seen many posts regarding them nv, efs and qcn but you seem to be fixated on the term imei so lets just let the post die or have it closed.
I understand what you are saying in regards to imei but that is just a part of nv efs and qcn backups. it is a risk that everyone takes when modding or customizing their phones, so backing them up and restoring as needed is always recommended.
If you have a backup of your EFS, simply restore it. That is straightforward, easily done and not controversial.
I thought you said you hadn't made a backup which is unfortunate. And I do have sympathy for the situation. But as you just said that is an expected risk of modding our phones. Having a broken phone isn't cause to ignore a set of rules that say this topic is forbidden due to abuse.
.
Hey mate,
I had almost the same problem. After a few days i finally got my phone working by doing what is in this post:
http://forum.xda-developers.com/showpost.php?p=55953093&postcount=29
Good luck and let me know if you need any help or if what i did isn't clear and i can give you some proper instructions. Make sure you backup everything before you do this just in case something even worse happens.
Mod Edit
Changing imei is illegal.
No such discussions are allowed on XDA.
Thread closed
malybru
Forum Moderator